Recent Azure DevOps article about Flaky test management mentions custom detection of Flaky Tests, but I can't find any documentation about how to implement that.
I thought it might be part of Publish test results task but I see no mention of Flaky Tests in there.
There is indeed a missing of documents about how to implement custom flaky test detection.
I reported this issue to microsoft developer community. you can keep track on this thread
Related
There are many reasons why Azure DevOps (ADS) pipelines may raise warnings but continue execution (for example due to bad task design). As pipelines are often part of an automated workflow (e.g. nightly builds, pull request validation builds), the pipeline result page will not be looked at by a human in most cases. As a result, those warnings may be left unnoticed or ignored for a very long time.
To make sure that these warnings are taken care of, I would like to make them fail the pipeline, similar to the --fatal-warnings flag commonly used in compilers.
I tried searching the official docmentation, Microsoft's issue tracker on pipeline tasks and the internet for similar flags, but I could not find anything useful.
Do you have any idea how to make warnings in ADS pipelines harder to miss and ignore?
I ran the build but failing with below errors. I have corrected the code but not sure what is the cause for this.
And Every time I have chosen Agent specification VS2017-Win 2016 but it is taking different one it seems after I noticed build was run. why it happening. Please help.
It is ASP.NET build.
Recently Microsoft has been battling Bitcoin miners on their pipelines platform. To combat this, they've added additional validation to ensure you are you and your intent isn't nefarious.
They've taken away all the free pipelines from accounts by default and you need to fill in a form to contact support to get these pipelines reinstated.
The link to the form is in the red error message that is rendered in your build log.
So I´m looking at the Agile Workflow in Azure DevOps and I´m wondering, what´s the purpose of the Feature work item?
I´ve used Jira a lot and we only used Epics->User Stories->Tasks.
I can´t fine any good explanation to why Microsoft has added this WIT to their default workflow.
See here, Adding Features and Epics
I think of it this way, you would define a feature flag around code for a feature because it's a single shippable unit of testable code, but you wouldn't do the same for an epic because it's a hodgepodge of stories related to a business initiative. Having the two WITs allows you to clearly delineate those two needs and to map the user stories accordingly.
I'm looking for a CI solution that allows me to do acceptance testing across my app's multiple container-based services. Does CodeShip support that?
I have put in a request to discuss this with their sales dept but their documentation led me to believe this was a better place for the question.
I need a tool that will graphically represent our build pipeline. The below screenshots of ThoughtWorks Go and the Jenkins Pipeline plugin illustrate almost exactly what I want it to look like.
The problem is that we already use Jenkins for our builds and deployments, along with a few other custom tools for orchestration type duties. We don't want a pipeline tool to do the builds or deployments itself, it just needs to invoke Jenkins! I tried out Go, and the first thing it asked for is where my source code is and how to build it. I couldn't get Go to work in a way where Jenkins does the builds but Go creates the pipeline.
I've also experimented with the Jenkins Pipeline plugin, but it's very limiting. For one, it doesn't work with the Join plugin (so we can't have jobs run in parallel, which is a requirement). It also assumes that all of our tasks happen in Jenkins (Jenkins can't see outside of our test lab and into our production environment). I don't know if this is a viable option either.
So, does anyone have any recommendation for some pipeline tools that will do what I'm looking for?
Edit (03/2018)
Since writing this question in 2012 and answering it in 2014, numerous tools have come online to support what I originally wanted. Jenkins now supports scripted pipelines natively and has an excellent UI (Blue Ocean) for rendering them. Those stumbling on this question should consider using these for their pipeline needs.
https://jenkins.io/doc/book/pipeline/
https://jenkins.io/projects/blueocean/
End edit
(Old answer)
It didn't exist when I asked the question, but Jenkins' Build Flow Plugin does exactly what I needed, and creates pipeline views very well.
https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin
Jenkins/Hudson can certainly be used to achieve a real pipeline.
You could use Go if you used a dummy material (an empty git repo, for example), and then used the API to trigger a pipeline and upload artifacts.
But, that's quite some effort, and you should probably only do that if you have a very good reason otherwise to use Go.
You can try with GoCD pipeline. It has very nice features for continuous delivery and has nice dashboard also which shows real time flow and status. Give a try.