Missing cloudsmith repo for stable code

[leamas]

There is a need to separate the test builds, always deployed, and the stable release builds. The primary reasons is that these have different retention policies: stable releases are kept for a long time, old test builds needs to be shredded just to keep the number of files sane.

Here are two things: A need to define a new cloudsmith repo like squiddio-stable or so, and code to send release to the new stable repo. The overall idea would be to consider tagged builds as stable whereas untagged commits are test builds.

Of course, this has some meaning with respect to #71. Assuming that using more than one repo doesn't really work on github we still need to keep at least the installer artifact on cloudsmith => this becomes a logical step.

However, it has nothing to do with the handling of the manual packages currently on github. This is one of the overall issue sin #71.

[leamas]

I do have a question about "unstable" being on cloudsmith, because I find the current OpenCPN system very nicely integrated with...

Why would this be affected?! Using cloudsmith does not change how we use git or github. They are just not related. The only difference is deployment.

[leamas]

Is the use of "Unstable" slightly different and to be used for test runs of OpenCPN before stable deployment & release?

Yes

[leamas]

Also, again, let's stick to the subject. This issue is about a repo for stable installer artifacts. It has nothing to edo with what's currently on Github. Which I described in my initial post.

[rgleason]

Sign up for Cloudsmith service with your github account

You may be asked to add a regular sign in later, or that may be circleci I am thinking of. Then using your cloudsmith account From Cloudsmith API User > Settings > API Keys (number)

• into Circleci Settings> mauroc> squiddio_pi> Env Variables "CLOUDSMITH_API_KEY" (number)
• into Appveyor Projects> squiddio_pi> settings> Environment "CLOUDSMITH_API_KEY" (number)
• Does Travis need the cloudsmith api key too? - I don't think so.

[rgleason]

Yes, I saw, that you have Cloudsmith setup. Is your Cloudsmith approved to run MacOS? I guess it is still running...

!/bin/bash --login -eo pipefail

ci/circleci-build-macos.sh

[mauroc]

I didn't know cloudsmith had to be approved for macos? Isn't it just a hosting platform?

On Tue, Oct 22, 2019 at 2:22 PM Rick Gleason notifications@github.com wrote:

Yes, I saw, that you have Cloudsmith setup. Is your Cloudsmith approved to run MacOS? I guess it is still running...

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mauroc/squiddio_pi/issues/74?email_source=notifications&email_token=AAGRYLXM5NB4JMWQFQIGE43QP5VKDA5CNFSM4JCVRCCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB7ICSQ#issuecomment-545161546, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGRYLRMKYAHVR2GJFNASADQP5VKDANCNFSM4JCVRCCA .

-- sQuidd.io

[rgleason]

mauro, I just emailed you, Jon and Alec, the authorization note that I just got from support. Perhaps you got approved awhile ago?

[leamas]

@rgleason: Could you please stick to the subject? The subject here is basically a request from me to @mauroc to add some new repos in the squiddio cloudsmith instance...

[leamas]

Please: could you stick to the subject? I'm basically doing a request to @mauroc tp create a single new cloudsmith repo. And that's it.

So please don't pull in all sorts of other aspects, most of which related #71, still to be settled.

There are signs that @mauroc actually has a life and cannot respond the same day. This is just how things are. So hold your horses. If you have anything to say about my request to create a new single cloudsmith repo do so, but otherwise I suggest that you just wait until we have some feedback from @mauroc on #71.

There is also a (slim) chance that @mauroc actually understands what this issue (#74) is about and provides some feedback. It's not easy in all his noise, and I wouldn't take it for granted...

[mauroc]

A need to define a new cloudsmith repo like squiddio-stable or so, and code to send release to the new stable repo.

I have just created https://cloudsmith.io/~mauro-calvi/repos/squiddio-stable/packages/ let me know if this is going to work.

[mauroc]

There are signs that @mauroc actually has a life and cannot respond the same day. This is just how things are.

Yes, I do have a life, just like all of you I am sure, but that doesn't mean I don't want to be responsive. I have had a medical issue lately that has taken a lot of my time, but I am determined to help this process as much as I can. I think I understand the intent of #74.

I will say that I do find the constant stream of information very confusing, particularly since everything is oranized around issues, and PRs, I tend to loose the thread of the overall conversation. I don't want people to change the way they work, but If you guys ever want to move to Slack, I have created a squiddio channel that we can use. Up to you.

[leamas]

let me know if this is going to work.

It will work just fine. Thanks! Closing.

[leamas]

I will say that I do find the constant stream of information very confusing, particularly since everything is oranized around issues, and PRs,

Indeed. Discussions on issues and PRs are valuable, but requires some discipline to work. Discipline isn't easy; neither for me nor anyone else, I guess.

I don't want people to change the way they work, but If you guys ever want to move to Slack, I have created a squiddio channel that we can use. Up to you.

I have used slack in some $ projects, but it was some time ago. Let's see if I can get slack running on my linux box, I'll let you know. This is certainly the kind of tool needed to clean up the github discussions.