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

[azure-pipelines] add vcpkg pipelines #151

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Conversation

Raffaello
Copy link
Owner

@Raffaello Raffaello commented May 23, 2020

updates:

  • win
  • mac
  • linux
  • analyzer

@Raffaello Raffaello added configuration cmake or project related code, configuaration enhancement New feature or request labels May 23, 2020
@Raffaello Raffaello added this to the Better CI milestone May 23, 2020
@Raffaello Raffaello changed the title [azure-pipelines] add vcpkg dependencies pipeline [azure-pipelines] add vcpkg pipelines May 23, 2020
@Raffaello Raffaello force-pushed the 107-vcpkg-pipeline branch 6 times, most recently from 2475727 to f89860f Compare May 23, 2020 16:15
@Raffaello Raffaello force-pushed the 107-vcpkg-pipeline branch from f89860f to 6ff1833 Compare May 23, 2020 16:27
@Raffaello
Copy link
Owner Author

after some consideration and extra complication for the triggered pipeline to use the right branch.
there is also no need to triggers the other pipeline after the vcpkg pipeline building dependencies.

at the end is the same number of steps, except for the analyze pipeline (1 extra same vcpkg macos dep stage), than running one full vcpkg pipeline before.

In the current way, each pipeline is self-dependent with dependencies too.

in the new way, would be just enough to download the artificat, in case it doesn't exists should be trigger the vcpkg build.

there is no too much reason to do this extra effort at the moment, also because it might overcomplicate this CI pipelines....

just trying for a little while now.. but i won't merge it i think...

@Raffaello
Copy link
Owner Author

i think is not triggered because is the default master branch yml file used with the triggering pipeline, so i should merge to test if it is triggered.

but as i considered, i don't want at the end in this way.

@Raffaello Raffaello added the wontfix This will not be worked on label May 23, 2020
@Raffaello Raffaello self-assigned this May 23, 2020
@Raffaello Raffaello linked an issue May 23, 2020 that may be closed by this pull request
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
configuration cmake or project related code, configuaration enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[azure-pipelines | dep] reusing same Dep stage
1 participant