Info: TravisCI about st2-packages HOT 9 CLOSED

Thank you for the detailed review. Now we can keep travis in our view scope. Nice!)

The first - yeah unpredictable build time is bad, but I've seen it before with a dedicated cloud node, better to have a good cloud...)

The second yeah this sucks, so travis doesn't provide us a way to do the required action (publish packages somewhere) from the box.

Third, no no we don't want and need to tie up to our existing travis workflow. We rather want to untie and simplify the "test on a git commit" stage.
It's clear that we need another CI instance for the task of building packages, and it should be triggered via argument enabled hook, this is the best case. What I mean by an argument enabled hook is that a person can initiate a build say it: build debian with arguments repo=st2-packages branch=master st2ver=0.15 st2rel=dev15.

from st2-packages.

There are 2 cool things about Travis I've found today also:

• Uploading Artifacts to S3 via Travis CI
• GitHub Releases Uploading via Travis CI

from st2-packages.

1. drone also has it..., but probably we won't need s3 feature at all. Since our plan to use bintray.com.
2. yeah, nice +1

I've just had a short look into the second thing, and was surprised - github_key goes in the travis.yml so it's seems to be public. Can you clarify this moment?

from st2-packages.

They most probably mean encrypted by Travis keys, see: http://docs.travis-ci.com/user/encryption-keys/ (same logic with keeping secrets encrypted, as you might have in any Configuration Management tool).

Also it's possible to set ENV variables in Travis UI.

from st2-packages.

@armab have a look https://github.com/drone/drone/tree/master/plugin/publish
wow, it seems quite extensive. And there's bintray plugin already available)

from st2-packages.

Nice! Drone plugin directory is definitely something we should dig into. The bad thing is that I can't find plugin dir in 0.4 branch (as you said parallel support starts from this version): https://github.com/drone/drone/tree/0.4.0 Must be hidden somewhere.

Just found that Travis has built-in deploy to Bintray also: http://docs.travis-ci.com/user/deployment/bintray/

Here is another bash example via Bintray API (simple CURL POST): https://github.com/bintray/bintray-examples/tree/master/bash-example

Ok, at least I hope we won't have problems uploading to Bintray.

from st2-packages.

Btw, nice page here: http://addons.drone.io/ 🍰
We should have something nice looking like this for StackStorm packs/integrations.

from st2-packages.

yeap. bintray has its API, however less scripting is what we need. So it's nice that we've got already ready bintray integrations for travis and drone, so no need in wheel reinvention)

from st2-packages.

okay Travis is not our option, we've chosen Circle CI (details here #6), so closing it.

from st2-packages.