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

CI pipeline #64

Closed
4 of 5 tasks
frosklis opened this issue Mar 15, 2021 · 2 comments
Closed
4 of 5 tasks

CI pipeline #64

frosklis opened this issue Mar 15, 2021 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@frosklis
Copy link
Collaborator

frosklis commented Mar 15, 2021

I made a mistake publishing a tag that didn't match the cargo version. This simply cannot happen. In fact it should be fully automated.

Modify travis set-up so that when a tag is created:

  • It is checked that the tag name matches the Cargo.toml version.
  • The binaries are packaged into the release version.

When a commit is done to master:

  • Create a release which is a pre-release with some suffix.

When a new tag is published:

  • Auto upload to crates.io
  • Bump version automatically
@frosklis frosklis added the enhancement New feature or request label Mar 15, 2021
@frosklis frosklis self-assigned this Mar 15, 2021
frosklis added a commit that referenced this issue Mar 15, 2021
The reason for this is that ```tarpaulin``` gets run.
frosklis added a commit that referenced this issue Mar 15, 2021
- Automatically create a tag for everything that affects the master
branch.
- When tagging, check that the tag name matches the Cargo version.
frosklis added a commit that referenced this issue Mar 16, 2021
frosklis added a commit that referenced this issue Mar 16, 2021
frosklis added a commit that referenced this issue Mar 16, 2021
frosklis added a commit that referenced this issue Mar 16, 2021
frosklis added a commit that referenced this issue Mar 16, 2021
frosklis added a commit that referenced this issue Mar 17, 2021
@frosklis
Copy link
Collaborator Author

Decided against building pre-releases automatically. If a user wants to check on the latest developments, it is because it is an advanced user that can install from source.

frosklis added a commit that referenced this issue Mar 20, 2021
frosklis added a commit that referenced this issue Mar 20, 2021
frosklis added a commit that referenced this issue Mar 21, 2021
frosklis added a commit that referenced this issue Mar 21, 2021
frosklis added a commit that referenced this issue Mar 22, 2021
frosklis added a commit that referenced this issue Mar 22, 2021
frosklis added a commit that referenced this issue Mar 22, 2021
frosklis added a commit that referenced this issue Mar 22, 2021
frosklis added a commit that referenced this issue Mar 22, 2021
make the main.yaml necessary for pull requests #64
frosklis added a commit that referenced this issue Mar 22, 2021
Fix folder names #64
frosklis added a commit that referenced this issue Mar 24, 2021
automatically bump version for development #64
frosklis added a commit that referenced this issue Mar 29, 2021
frosklis added a commit that referenced this issue Mar 30, 2021
@frosklis
Copy link
Collaborator Author

frosklis commented Aug 7, 2021

Tried to bump version automatically but it failed when pushing to github again. We'll see if it works in the next release 0.28.0

frosklis added a commit that referenced this issue Aug 16, 2021
frosklis added a commit that referenced this issue Aug 16, 2021
frosklis added a commit that referenced this issue Aug 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant