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

T2 quantum first release #16394

Merged
merged 4 commits into from
Jan 29, 2021
Merged

T2 quantum first release #16394

merged 4 commits into from
Jan 29, 2021

Conversation

00Kai0
Copy link
Contributor

@00Kai0 00Kai0 commented Jan 28, 2021

SDKAuto and others added 2 commits January 28, 2021 03:14
Update quantum python track2 config (Azure#12566)

* update quantum python track2 config

* Update readme.python.md

Co-authored-by: msyyc <70930885+msyyc@users.noreply.github.com>
@check-enforcer
Copy link

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run python - [service] - ci

@00Kai0
Copy link
Contributor Author

00Kai0 commented Jan 28, 2021

/check-enforcer override

@00Kai0
Copy link
Contributor Author

00Kai0 commented Jan 28, 2021

/azp run

@azure-pipelines
Copy link

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

@jsntcy
Copy link
Member

jsntcy commented Jan 28, 2021

/azp run prepare-pipelines

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jsntcy
Copy link
Member

jsntcy commented Jan 28, 2021

/azp run

@azure-pipelines
Copy link

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

@jsntcy
Copy link
Member

jsntcy commented Jan 28, 2021

/azp run python - quantum - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jsntcy jsntcy merged commit 250e123 into Azure:master Jan 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants