2020-11-29 06:20:25
*https://github.com/snowblossomcoin/rosesnow/compare/82087b7eef6e...b48a714667cb*
https://github.com/snowblossomcoin/rosesnow/commit/b48a714667cb048fc3dfcc0f5fa51adfae8b7df4 - Update configs
GitHub
2020-11-29 08:25:29
None
2020-11-29 08:47:45
*https://github.com/snowblossomcoin/rosesnow/compare/b48a714667cb...6b2eb1d48af1*
https://github.com/snowblossomcoin/rosesnow/commit/6b2eb1d48af1d2cd97c9bb8f8265a1e41b30fd8a - Update cli config
GitHub
2020-11-29 17:45:48
@Clueless not sure why this won't build. https://hub.docker.com/repository/docker/snowblossom/rosetta-cli
Fireduck
2020-11-29 17:46:02
It should build using the dockerfile in the 'cli' directory
Fireduck
2020-11-29 17:46:08
not hugely important
Fireduck
2020-11-29 17:51:39
checking
Clueless
2020-11-29 17:56:37
at a glance it looks fine, dockerhub just flashes when I press "trigger" and nothing happens.
Clueless
2020-11-29 18:00:07
I'd declare this an issue with dockerhub
Clueless
2020-11-29 18:00:49
yeah, probably something about being in the subdir to do the build
Fireduck
2020-11-29 18:00:51
but I don't know
Fireduck
2020-11-29 18:01:05
it isn't worth a lot of investigation, I can easily just push a new version as needed
Fireduck
2020-11-29 18:01:14
and really no one is likely to run it from docker other than me
Fireduck
2020-11-29 18:02:31
I'll want automatic builds on the other (rosetta) but we will need to split out the docker files. The rosetta spec calls for doing it in a somewhat odd way, they want the dockerfile to pull the git source rather than just using what is in the current repo.
Fireduck
2020-11-29 18:06:05
So we can make one that does exactly what they are asking for
Fireduck
2020-11-29 18:06:21
and one that uses current repo and have that set to build on push
Fireduck
2020-11-29 18:24:04
only on main branch?
Rotonen
2020-11-29 18:24:43
Yeah
Fireduck
2020-11-29 18:26:33
Also, what are branches? https://www.gstatic.com/allo/stickers/pack-880502/v2/xxhdpi/10.gif 420x420px image
Fireduck
2020-11-29 20:24:37
@Fireduck subdirectories are pretty normal, I believe dockerhub is just bugging out.
Clueless
2020-11-29 20:26:57
alright, I looked again, javascript console reports `errorMessage: "Branch 'master' not found"`
Clueless
2020-11-29 20:27:16
oh, it is main or something
Fireduck
2020-11-29 20:27:24
and, apparently it's been named "main"
Clueless
2020-11-29 20:27:25
because master is racist
Fireduck
2020-11-29 20:27:58
I vote for keeping with convention in this case. :P
Clueless
2020-11-29 20:28:03
I'll go rename anything that says "slave" to "comerade-worker"
Fireduck
2020-11-29 20:28:26
the convention has changed. :wink:
Fireduck
2020-11-29 20:28:32
wait really
Clueless
2020-11-29 20:28:40
yeah, github new default is main
Fireduck
2020-11-29 20:32:46
Alright, so I renamed the output docker tag to "dev", because "latest" would interfere with pointing to latest tags being built.
So, the latest commit would be "dev", and latest release would be "1.2.3" sound reasonable?
Clueless
2020-11-29 20:34:00
and if there are multiple types, perhaps /cli/ should be cli-dev and cli-1.2.3 ?
Clueless
2020-11-29 20:34:31
triggers build
Clueless
2020-11-29 20:34:58
so the cli will be in snowblossom/rosetta-cli
Fireduck
2020-11-29 20:35:07
the other docker image goes in snowlbossom/rosetta
Fireduck
2020-11-29 20:36:01
if that's the convention they/you want, sure.
Clueless
2020-11-29 20:37:51
if cli is just a specific sub component of the repo, I personally generally prefer: `snowblossom/rosetta:cli-1.2.3` I think. but I'm a newb.
Clueless
2020-11-29 20:38:19
None
2020-11-29 20:38:37
heh, renaming that to your convention.
Clueless
2020-11-29 20:39:15
yeah, they are completely different things that do different things
Fireduck
2020-11-29 20:39:28
the tag name (after the colon) is for different versions of the same concept
Fireduck
2020-11-29 20:39:37
at least that is how I see people using it
Fireduck
2020-11-29 20:40:26
I know this is just bikeshedding, but I view the repo as just being "the software" and the tag being a version or specific offshoot of it.
Clueless
2020-11-29 20:40:56
I see what you are saying
Fireduck
2020-11-29 20:41:07
but the docker user doesn't care where it comes from
Fireduck
2020-11-29 20:41:19
so in my mind it is org/function:version
Fireduck
2020-11-29 20:41:30
version being latest or stable or version numbers
Fireduck
2020-11-29 20:42:13
@Fireduck well, do you want a specific output?
My default is: rosetta-cli:dev for latest commit and rosetta-cli:1.2.3 for tags?
or do you want to configure it?
Clueless
2020-11-29 20:42:31
that sounds perfect
Fireduck
2020-11-29 20:47:28
None
2020-11-29 20:50:03
Also, I personally try to make sure latest typically points to latest release, for user friendliness.
Typically I don't expect :dev to always be working. I need to read up on how `latest` tag is used though. I think it automatically points to the last pushed tag?
Clueless
2020-11-29 20:50:18
None
2020-11-29 20:52:09
dunno what triggered that one, but okay. :shrug:
Clueless
2020-11-29 21:01:34
Ha
Fireduck