PR #83 - stable versions testing

[mauroc]

the unstable packages were all deployed correctly from circleci and appveyor for an untagged release

The stable packages did not deploy to squiddio-stable. The process I followed in this case was:

# updated version to 1.0.17.3 in Cmakelists.txt
git commit -am 'v 1.0.17.3'
git tag v1.0.17.3
git log # showed latest commit is tagged correctly as v1.0.17.3
git push origin v1.0.17.3 # this one did not trigger the circleci builds. Only appveyor
git push origin master # this one triggered all the builds, but none were deployed to squiddio-stable

what am I doing wrong? I feel we are so close....

[rgleason]

Maybe you put the tag in the ci/circleci-uploads.sh ? Sort of a pain.

[mauroc]

I didn't and would not know where in that file they would go. The issue also affects the appveyor build, not just circleci

[rgleason]

This should work, provided you issue it quickly enough. The problem is appveyor builds quite quickly. So maybe make the tag before pushing the commit. git tag v1.0.19.1 Then push git push origin v1.0.19.1

I've had appveyor complete before I did the git push origin v1.0.19.1 and there is no file pushed, it just stops.

Don't know about the circleci / cloudsmith

[leamas]

You missed git push --tags. Without the --tags option the tag is not visible in the github account.

[leamas]

BTW: The links provided by @rgleason are not relevant, we are not using this kind of functionality.

[rgleason]

Alec That is not correct they are visible without the tags option. I've been using it this way and they are clearly visible in the Tags tab under Releases.

[leamas]

This issue is about the cloudsmith deployment of installer artifacts, nothing else. They have never been available on github.

[leamas]

Could you please stick to the subject? Which is problems deploying the installer artifacts on cloudsmith. Full stop.

Yes, tags are of course visible on github. But it has nothing to do with the subject.

[leamas]

Going back to the problem, we have the following log building c4d5cf6

++ git rev-parse --short=7 HEAD
+ commit=c4d5cf6
++ git tag --contains HEAD
+ tag= 

The log means that there is no tag visible which points to c4d5cf6. This might be because the tag isn't pushed -- according to initial logs it isn't. It could also be because while it exists it doesn't match c4d5cf6 i. e. there was a commit after the tagged one.

[leamas]

@rgleason: You could also just check the tags available in the github interface (tags, not releases!). V1.0.17.3 is not there. Could we now stop this confused discussion?

[mauroc]

success! (didn't know about the --tags option). All 10 artifacts are uploaded to the stable repo See them in all their digital splendor. Amazing work guys

[mauroc]

I wrote the following to myself. I don't deploy new releases very often, so I am sure the next time I will have forgotten most of the process. I thought it may be useful for our online docs, as an intro to a more technical step-by-step. It would also be useful to include guidelines for the PA (plugin admin) in terms of

• keeping their repos clean of old artifacts

• what belongs in the stable release? I.e. major releases? Minor releases? Patches? etc.

  CONTINUOUS INTEGRATION for Plugins We use 2 CI services: -Appveyor (Windows only)

• Circle CI (all others) ...and one 'hosting service' for executables:
• Cloudsmith I have created accounts on all 3 using github oauth. (will each plugin admin need to do this?) The CI cycle is automatically triggered on both CI services by a git push to github . The CI services are essentially notified by github through a callback that a new version is available, and they pull the code and compile it in a temporary VM, which is then destroyed after the deploy. Note that only push'es to the master branch trigger the build! At the end of the CI cycle, the artifacts get uploaded to Cloudsmith if the builds are successful There are 2 repositories on Cloudsmith
• mauro-calvi/squiddio_pi: -- ALL builds get deployed here, if successful. Each cycle currently generates 10 artifacts (5 platforms: mingw, macos, debian , windows and flatpack. Each platform has 2 packages: one executable and one xml file used by the installer). This repo needs to be cleaned of old artifacts periodically
• mauro-calvi/squiddio-stable: -- this only contains the official production releases (probably only the last 2-3, to keep clutter at a minimum). Upload to this repository is triggered if and only if: ---the latest commit has a tag associated with it , use e.g. git tag v1.0.17 to tag the HEAD commit ---it is pushed with the --tags option, e.g. git push --tags origin master

[leamas]

This repo needs to be cleaned of old artifacts periodically

There is actually a retention policy setting for the cloudsmith repo you could set to just keep the last say 30 packages or so.

[rgleason]

I thought that for free opensource, retention policy is automatic.

[leamas]

Nope. You can find the Retention Rules settings in the left pane after pushing the Set Me Up button in the cloudsmith repo.