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

Set up continuous integration #7

Open
gberche-orange opened this issue Feb 23, 2016 · 1 comment
Open

Set up continuous integration #7

gberche-orange opened this issue Feb 23, 2016 · 1 comment
Milestone

Comments

@gberche-orange
Copy link
Member

gberche-orange commented Feb 23, 2016

compile, run unit tests, package as a jar/war, run acceptance tests, create a maven release, upload the release into the github repo

@gberche-orange gberche-orange changed the title Set up concourse CI Set up continuous integration Mar 14, 2016
@gberche-orange
Copy link
Member Author

@s-bortolussi Thanks for the travis-ci integration.

Would be great to enhance the travis-ci release script in the following ways:

  • avoid having variations in the name of the produced war (currently static-creds-broker-1.1.war) across release, as to:
    • avoid the need to manually update the deployment procedure
    • be able to hardcode the relative path to the binary in manifest.yml with "path" property
  • find a better name for the enclosing directory (currently "to-release") suggesting "static-creds-broker" instead, and investigate if there is a way to directly include the war file into "."

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

2 participants