Skip to content
This repository was archived by the owner on Aug 18, 2020. It is now read-only.

Automate various release related tasks #134

Closed
5 tasks done
hlxid opened this issue Sep 27, 2019 · 0 comments
Closed
5 tasks done

Automate various release related tasks #134

hlxid opened this issue Sep 27, 2019 · 0 comments
Assignees
Labels
enhancement New feature or request major Needs a major platform / framework / build environment rework

Comments

@hlxid
Copy link
Member

hlxid commented Sep 27, 2019

Description

Release related tasks should be automated if possible to reduce the work/burden of creating releases. I would want to use GitHub Actions for the following tasks:

We currently use Travis CI for the wiki sync and for uploading the generated documentation to codeoverflow-org/chatoverflow-gh-pages, but I think that Travis doesn't scale really good because you can do all tasks in the travis build after each other, which is slow, or can create a job for each but then the .travis.yml gets really big and unmaintainable at some point. I'm open for other suggestions on this.

For #52 we also need a CI system. It should obviously compile our code (and run tests once we have some) and publish a snapshot release of the api to the Sonatype snapshot repository.
This may also be done using Actions, but since I couldn't test it yet and don't know how good it is I am also fine with any other CI system.

  • A simple CI for the beginning
  • Document all changes in the wiki

Note that Actions will be released for the public on November 13th.

@hlxid hlxid added enhancement New feature or request major Needs a major platform / framework / build environment rework future This issue is not relevant for the current development, but will become important in the future labels Sep 27, 2019
@hlxid hlxid added this to the alpha 1 milestone Sep 27, 2019
@hlxid hlxid self-assigned this Sep 27, 2019
hlxid added a commit to codeoverflow-org/chatoverflow-wiki that referenced this issue Dec 24, 2019
@hlxid hlxid closed this as completed Dec 24, 2019
@sebinside sebinside removed the future This issue is not relevant for the current development, but will become important in the future label Dec 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request major Needs a major platform / framework / build environment rework
Projects
None yet
Development

No branches or pull requests

2 participants