Restructuration for community content #169
Merged
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
- Move sources (code) to a `source` folder - Move metadata, resources, and subdomains for communities into communities folder where each community has its own subfolder - Move results back to the main branch, in the resources folder
- Merge weekly workflows into 1 workflow that wil open a PR with the changes - Update other workflows to the new structure
paulzierep
reviewed
Sep 16, 2024
| name: Fetch tool stepwise and merge, fetch tutorials and filter the resources for communities | ||
| strategy: | ||
| max-parallel: 1 #need to run one after another, since otherwise there is a chance, that mulitple jobs want to push to the results branch at the same time (which fails due to merge) | ||
| matrix: |
There was a problem hiding this comment.
This combined WF triggers a subset job, where each repositories*.list is processed individually. The way it's now combined, everything after the merge part does not really make sense ... and the Fetch list of all available servers should probably also not be a part of the matrix subset. I would propose to run the Fetch all tool stepwise in an individual job and store the results as an artifact. Then use the artifact as input for the merge part and have that as another job.
There was a problem hiding this comment.
I adapted the CRON workflow to have 3 jobs
- For getting the available servers and storing the TSV as artifact
- For triggering the subset jobs to fetch tools in parallel and storing the outputs as artifact
- For merging the TSV and running the rest
…ts to share btw jobs
bebatut
force-pushed
the
restructure
branch
from
4e72582
to
051460a
Compare
paulzierep
reviewed
Sep 16, 2024
| runs-on: ubuntu-20.04 | ||
| name: Fetch tool stepwise | ||
| strategy: | ||
| max-parallel: 1 #need to run one after another, since otherwise there is a chance, that mulitple jobs want to push to the results branch at the same time (which fails due to merge) |
There was a problem hiding this comment.
With this nice new job logic, we can also run all this jobs at the same time.
paulzierep
approved these changes
Sep 16, 2024
Co-authored-by: paulzierep <paul.zierep@googlemail.com>
This was referenced Sep 19, 2024
Merged
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.
Fix #164
sourcefoldermainbranch protected)