search

AtlassianPS / JiraPS

PowerShell module to interact with Atlassian JIRA
https://AtlassianPS.org/module/JiraPS
MIT License
323 stars 131 forks source link

Set up CI with Azure Pipelines #317

Closed azure-pipelines[bot] closed 5 years ago

azure-pipelines[bot] commented 5 years ago

implements AtlassianPS/AtlassianPS#10

kaylangan commented 5 years ago

I'm a Program Manager on Azure Pipelines. Let me know if you have any questions or suggestions. I'm happy to help!

Dejulia489 commented 5 years ago

@lipkau , I am the Author of AzurePipelinesPS. I have my AzurePipelinesPS pipeline setup in Azure Pipelines. Let me know if you need any assistance.

lipkau commented 5 years ago

Thank you, @kaylangan . I am really enjoying working with VSTS. But I found 2 things which are bugging me a bit:

This is all the feedback I have for now. But I really appreciate the product and the upgrade free tier you provide. Helps a lot for hobby projects, like this/these one/s.

lipkau commented 5 years ago

@Dejulia489 : why don't you put your pipeline in the pipeline yaml file? or delete the file from the repo?

Dejulia489 commented 5 years ago

@lipkau, I built my build pipeline from a json template with AzurePipelinesPS. I have update my yml to reflect my build.

shashban commented 5 years ago
  • I tag the commit which was released in the git(hub) repo in the last step of the CI/CD. And as the "release pipeline" does not have a task for cloning the repository, nor a variable of the commit which is being built (so that I can manually fetch the right commit), I am unable to use the "release pipeline" for deploying my project - I have to do it as a conditional step in the "build pipeline"

For adding "tag a commit" in the release pipeline, you can use the variable Release.Artifacts.{alias}.SourceVersion

davidstaheli commented 5 years ago

Update: the ability to upload build artifacts from a fork PR build should be available in Azure Pipelines production by the end of next week (November 9) - hopefully sooner.

lipkau commented 5 years ago

thank you for the hint, @shashban .

If I understand you correctly, I should be able to open the repo on the correct commit with something like this:

git -c http.extraheader="AUTHORIZATION: basic ***" -progress clone .....
git checkout --progress --force $(Release.Artifacts.{alias}.SourceBranch)

is this correct?

lipkau commented 5 years ago

Thank you so much for the update @DavidStaheli . I was visiting this ticket daily to check on this :-P https://developercommunity.visualstudio.com/content/problem/350007/build-from-github-pr-fork-error-tf400813-the-user-1.html

davidstaheli commented 5 years ago

😄 I'm glad you brought it up, @lipkau! I'll be sure to update that ticket and the one it links to as soon as this is available everywhere.

lipkau commented 5 years ago

@DavidStaheli : any news regarding the release?

davidstaheli commented 5 years ago

Hi @lipkau. Thanks for your patience. Unfortunately, it was delayed longer than I expected. The capability is deployed to production, but still behind a feature flag that should be enabled for everyone this week. If you can tell me the name of your Azure DevOps organization, I can enable it for you sooner.

lipkau commented 5 years ago

@DavidStaheli : my org is named AtlassianPS https://dev.azure.com/AtlassianPS /ConfluencePS

I appreciate your support