Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate build step for version + alias #31

Closed
SamVerschueren opened this issue Dec 16, 2015 · 6 comments
Closed

Separate build step for version + alias #31

SamVerschueren opened this issue Dec 16, 2015 · 6 comments

Comments

@SamVerschueren
Copy link
Contributor

I was thinking that it would be nice to have a separate step for creating a version and alias. I think it offers more flexibility.

  1. Update code and configuration
  2. Create alias for $LATEST (no new version is created)
  3. Create new version and alias the version (option to provide multiple aliases, maybe comma separated)

It would make conditionally applying versions and aliases a lot more easier.

How could this be integraded UI-wise? Leave it open to you but this is my suggestion.

  1. An input box for the region
  2. An input box for the lambda function
  3. Two checkboxes, one for Publish version and on for Assign Alias. Both can be checked or unchecked independently. If Assign Alias is checked, an input box popups up for creating the alias(es).

If Publish version and Assign Alias are both checked, a new version is created which will be aliased by all the aliases provided in the input box (comma separated).

If only Assign Alias is checked, the aliases will be applied to the $LATEST version.

Feedback is more then welcome :).

@msulland
Copy link

Hi,

We are in need of a similar feature, having a separate publish version step in our pipeline. Something like "AWS Lambda Publish Version" with version and alias as input enabling the publishing of a new version and updating an alias to point to it.

@msulland
Copy link

msulland commented Jul 25, 2016

I have now started to look at the possibility to add this to the code.

A totalt workflow will be like: build jar -> upload to lambda as $LATEST version -> test with payload -> publish $LATEST as new version -> point the alias currently used in production (for example ACTIVE) to the new version.

@msulland
Copy link

Hi, I have now completed the code extension and are putting the finishing touches on it.

@cast
Copy link
Contributor

cast commented Aug 9, 2016

Thanks msulland, I reviewed the pull request and merged it to this fork.
I will soon merge in the changes on the jenkinsci fork.

@cast
Copy link
Contributor

cast commented Aug 9, 2016

Included in release 0.5.4, arriving during the course of tomorrow in update panel.

@cast cast closed this as completed Aug 9, 2016
@SamVerschueren
Copy link
Contributor Author

Great work guys! Thanks for doing this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants