lourenco/mgmt - mgmt - código do assilvestrar

lourenco/mgmt

Fork 0

Commit Graph

Author	SHA1	Message	Date
Karpfen	7e8ced534f	misc: Use /usr/bin/env for a more generic shebang Use path based SHELL in Makefiles. It was suggested that this is a better solution for make for cases when there is no /usr/bin/env. See: https://github.com/purpleidea/mgmt/pull/694#discussion_r1015596204	2025-03-22 14:53:21 -04:00
James Shubin	6a7d904fae	misc: Improve tagging script This way we can push the tag after all the builds succeed. If something goes wrong, we can always delete our local tag and try again.	2019-10-04 06:49:04 -04:00
James Shubin	0ec00fe57f	make: Improve release pipeline Hopefully this makes releases a little better for users. In particular, this avoids listing old build artifacts in the SHA256SUMS files when we make new releases, and users can now download them directly. Now to make a release you run: `make tag && make release`. After the first make session ends, you'll have a new tag released publicly, and then during the second make session, the release target will notice this new tag, build some assets, and upload them!	2018-11-30 19:08:53 -05:00

Author

SHA1

Message

Date

Karpfen

7e8ced534f

misc: Use /usr/bin/env for a more generic shebang

Use path based SHELL in Makefiles. It was suggested that this is a
better solution for make for cases when there is no /usr/bin/env.

See: https://github.com/purpleidea/mgmt/pull/694#discussion_r1015596204

2025-03-22 14:53:21 -04:00

James Shubin

6a7d904fae

misc: Improve tagging script

This way we can push the tag *after* all the builds succeed. If
something goes wrong, we can always delete our local tag and try again.

2019-10-04 06:49:04 -04:00

James Shubin

0ec00fe57f

make: Improve release pipeline

Hopefully this makes releases a little better for users.
In particular, this avoids listing old build artifacts in the SHA256SUMS
files when we make new releases, and users can now download them
directly.

Now to make a release you run: `make tag && make release`.
After the first make session ends, you'll have a new tag released
publicly, and then during the second make session, the release target
will notice this new tag, build some assets, and upload them!

2018-11-30 19:08:53 -05:00

3 Commits