Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix integration test for merge in the main branch #63

Conversation

SimeonEhrig
Copy link
Member

If we want to merge in the main branch, we do it because we want to publish the package. Therefore, we need to be sure that there is an existing version of the dependent QED packages that works with the new version of the package we want to release. The integration tests are tested against the development branch and the release version.

  • The dev branch version must pass, as this means that the latest version of the other QED packages is compatible with our release version.
  • The release version can exist. If they exist, it means that we do not need to release a new version of this package.

I will open an test PR to test if the feature is correctly working. If it is working, I mark the PR for ready for review.

AntonReinhard
AntonReinhard previously approved these changes Sep 5, 2024
Copy link
Member

@AntonReinhard AntonReinhard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some documentation suggestions from my side.

.ci/integTestGen/test/generate_job_yaml.jl Outdated Show resolved Hide resolved
.ci/integTestGen/src/integTestGen.jl Outdated Show resolved Hide resolved
.ci/integTestGen/src/integTestGen.jl Outdated Show resolved Hide resolved
If we want to merge in the main branch, we do it because we want to publish the package. Therefore, we need to be sure that there is an existing version of the dependent QED packages that works with the new version of the package we want to release. The integration tests are tested against the development branch and the release version.
- The dev branch version must pass, as this means that the latest version of the other QED packages is compatible with our release version.
- The release version can exist. If they exist, it means that we do not need to release a new version of this package.
@SimeonEhrig SimeonEhrig force-pushed the fixIntegrationTestforMergeInMain branch from bf77d43 to da08934 Compare September 5, 2024 13:44
@SimeonEhrig
Copy link
Member Author

The pipeline looks like expected: QEDjl-project/QEDcore.jl#57

@SimeonEhrig SimeonEhrig marked this pull request as ready for review September 5, 2024 14:04
@AntonReinhard
Copy link
Member

Can you test it with a PR in QEDbase too? We should see the QEDprocesses Release test fail there.

@SimeonEhrig
Copy link
Member Author

Can you test it with a PR in QEDbase too? We should see the QEDprocesses Release test fail there.

Yes I can. I was actual wondering, why it didn't failed. Now, I know I choose the wrong QED project 😅
QEDjl-project/QEDbase.jl#117

@AntonReinhard
Copy link
Member

The test run in QEDbase was successful and working as intended 👍

@AntonReinhard AntonReinhard merged commit b7d3484 into QEDjl-project:dev Sep 5, 2024
3 checks passed
@AntonReinhard AntonReinhard added this to the Release-0.1.0 milestone Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants