[tests-only] Implement .drone.env #1567
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
to store the CORE_BRANCH and CORE_COMMITID for tests, the same way as is done in https://github.com/owncloud/ocis/blob/master/.drone.env
The disadvantage of having the commit-id embedded in
.drone.star
is that a.drone.star
in the PR branch gets used from the PR branch and if there are other, later, changes to.drone.star
inmaster
they do not take effect in drone CI. This can lead to confusion about exactly what pipelines ran with what settings in CI.Having
.drone.env
means that.drone.star
can be much less modified.Note: I had to change to
owncloudci/alpine:latest
(like inowncloud/ocis
) forcloneOc10TestReposStep()
because it used thesource
command, andowncloudci/php:7.4
complained thatsource
did not exist!