inspectit-ocelot icon indicating copy to clipboard operation
inspectit-ocelot copied to clipboard

Closes #1425 - Migrate Release Pipeline to GitHub Actions

Open aaronweissler opened this issue 3 years ago • 4 comments

Closes #1425


This change is Reviewable

aaronweissler avatar Sep 01 '22 09:09 aaronweissler

When merging, CircleCI must be deactivated in the project's settings.

aaronweissler avatar Sep 05 '22 08:09 aaronweissler

Currently Releases would be shown as created by github-actions user, if we want it to be by a specific user, e.g. NTTechnicalUser I think we need to just provide a personal access token of his to the release action, but the docs are not entirely clear on that, so we should test that once if wanted.

aaronweissler avatar Sep 12 '22 08:09 aaronweissler

Draft until NTTechnicalUser as releasing user

aaronweissler avatar Sep 12 '22 08:09 aaronweissler

Token has been added to code and environment secrets and functionality has been tested in fork.

aaronweissler avatar Sep 12 '22 09:09 aaronweissler

When trying to make a test-release I encounter two errors:

  1. Pushing the docker image results in the error message Cannot perform an interactive login from a non TTY device. Which may result because of the wrong credentials. Another answer from the internet suggested that it is because the $DOCKER_TAGenvironmental isn't set. But trying to set the variable did not fix the problem.
  2. When creating a new documentation results in the error message pathspec 'master' did not match any file(s) known to git

At the moment I have actions running, trying to fix the above mentioned error messages. For more information on how to maybe fixing the 2. issue I found the following stack overflow post: https://stackoverflow.com/questions/5989592/git-cannot-checkout-branch-error-pathspec-did-not-match-any-files-kn.

danipaniii avatar Jan 16 '23 10:01 danipaniii

I could fix the issue with creating the documentation and I started to implement the docker github action from the ocelot eum server, because I run into more errors with the login with the previous action. Unfortunately when building the docker image I get the following error: Screenshot from 2023-01-23 12-34-53

Extra info:

  • The entrypoint.sh is in the same directory as the Dockerfile
  • The inspectit jar is in the same directory and gets added without problem
  • Using COPY or ADD did not result in a different result

danipaniii avatar Jan 23 '23 11:01 danipaniii