Add needed secrets to make deployment work

[ctrueden]

With fea104f, I migrated the build from the no-longer-functional Travis CI system over to GitHub Actions. However, this repository still needs the SciJava secrets added, or else it won't be able to deploy snapshots or releases to maven.scijava.org.

The easiest way to set up the secrets would be to move this repository to an organization such as saalfeldlab that already has them.

@axtimwalde Otherwise, you'll have to go into Settings and paste them in there. I might be able to do it if you give me admin access to the repository, but I'm not sure; I haven't done this with other personal-account-based repositories yet.

[axtimwalde]

Oops... @ctrueden I tried to release, but I guess this issue does not allow the releases to be deployed. Can you help?

[ctrueden]

Sure, I ran mvn release:perform locally (with my deployment credentials) to finish the release. So mpicbg 1.5.0 artifacts are present on maven.scijava.org now. If you want the CI to be successful at that in the future, we can add the credentials as described above; let me know if/how you want to proceed there.

[axtimwalde]

Thanks!

[minnerbe]

It seems like this issue is not completely resolved, yet: deployment for the latest version 1.6.1 also failed (see here). I remember that this was also an issue for the 1.6.0 release, but iirc the credentials were not the main problem.

Any ideas what can be done to resolve this issue, @axtimwalde @ctrueden ?

[ctrueden]

The issue is the credentials. From the log:

Warning:  Skipping settings.xml generation (no deployment credentials).

So it appears @axtimwalde still needs to set them up.

[axtimwalde]

As last time, I am not sure what else to do. The secrets are here...

[ctrueden]

I am not sure what else to do.

As I suggested before, you could move the repository to an org and see if it works better. I recall that you already wrote to GitHub and their response was unhelpful. Another idea would be to create a new repository in your personal org, add the secrets there, and see if GitHub Actions can see them—i.e. troubleshoot whether it is this repo specifically that is glitched out, or just a problem with secrets + personal repos in general.