crabtaskworker.spec - temporarily uses private WMCore branch for py3-env #7502
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
status
ready to merge
tested, py3 specfiles here
description
Since our jenkins build job at every new tag build both crabserver and taskworker, replacing the
wmcverparameter in bothcrabserver.specandcrabtaskworker.spec, we need to port tocrabtaskworker.specsimilar changes as in #7496 .fyi: @belforte
PS: in
crabserver.speci moved back the version of WMCore, since it is going to be replaced anyway by jenkins. we can leave there the "desired" version, not the current one from my repo.