I'm looking for a way to run only failed pytests during last build.
I've tried --lf option for pytest but it did not help, I guess it is so because of teamcity.
Does anyone faced the same problem?
Thanks to usefull answer, I figured out what was wrong with teamcity.
Multiple builds were using same checkout directory, what caused problems.
As #grundic mentioned:
check that your working directory is not changing
use same agent
Related
I am trying to run runner on gitlab which is config with Fastlane through a pipeline, when I commit pipeline runs but failed every time. I am not sure what is the issue but it seems that my gitlab-ic.yml file is not working correctly
Did you installed java? Jdk or jre? Obviously your java path is wrong. You can post your config, so it is easier to find the problem.
I am running a custom Jenkins 2.263.4 build on Travis-CI. We need a fix with relative pathes that never made it into the Jenkins core...well for us it is mandatory.
Based on release 2.263.4 I applied the fix in core/SecretRewriter.java and core/VirtualFile.java and also changed the version name to give it branding. This worked very well in the past releases. But the last update we did was one year ago.
Now I am running into the error:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:3.2.1:shade (default) on project cli: Error creating shaded jar: duplicate entry: META-INF/services/io.jenkins.cli.shaded.org.apache.sshd.common.io.IoServiceFactoryFactory -> [Help 1]
I am not able to understand it at all.
Travis-CI is here: https://travis-ci.com/github/DanielWeber/jenkins
GitHub: https://github.com/DanielWeber/jenkins
I was not able to find this exact problem from somewhere else. I tried a bit with the shade config to set
<minimizeJar>false</minimizeJar>
and similar small things, but didn't really help.
My change is so small, I don't really understand what's happening.
If nothing helps, I might consider doing changes step by step then, rather than just merging the releae to our for, but hope someone sees the problem.
The issue is that the build is being execute two times based on the mvn install followed by mvn package which is defined in travis.yml file. This causes the issue.
Same configuration is working with window 10. but when i tried same configuration run with ubuntu, its showing an error.
error message while running with jenkins
The clean plugin cannot delete the named folder. Make sure the Jenkins has the right to delete the folder and that it is not locked in some other way.
By the way: Copy the text of your error into the question, don't make a bad photo.
Some process has hold of the file /home/xelpmoc-06/Documents/Doc/zerodha/target/classes/LoginZerodha/Zerodha/App.class.
Java process or Eclipse or some other program is doing some job with it. So that's why its showing that error. So please kill Java Process or restart Eclipse. May be your jenkins build failure, also can cause this to happen. So if nothing works out please restart your jenkins itself.
Here I am attaching a link that may be helpful to you. Please go through this. Hope this helps.
I got a Problem with our Jenkins Server:
The Config.xml files for the jobs are missing after some time and we dont know why.
I'm rather sure that noone is deleting the files.
I already uninstalled the Plugin email-ext as I first noticed missing jobs after I first installed the Plugin.
However this morning there was again 1 config.xml missing.
Jenkins Version is 1.598 and its running under win7.
I appreciate any hints on what could be the source of my problem.
Thanks in advance.
You can use Process Monitor to see which process deletes xml files.
I'm setting up Jenkins for the first time and running into an issue where Jenkins does not appear to even attempt to execute the Ant task I've specified.
I've defined my JDK and Ant installations under Manage Jenkins.
I've setup my Job to Invoke Ant using the Targets 'war-all'
Whether I force a build or wait for it to naturally execute after the next commit, there is nothing in the Build Console Output about attempting to execute the ant task.
Here is a sample Console Output:
Any ideas as to why it might not be executing would be appreciated. Also tips on how I can find more logging from Jenkins which might provide clues as to why it is not executing would be helpful. I'm not sure what Logger I might specify or even then where the logging information is written on the file system.
The problem was that I was selecting "Build multi-configuration project" as the type of my job. When I select "Build a free-style software project" as my job type the Ant task will execute after the SVN update.
Looks like your svn doesn't see any changes and therefor is not re-building the module.
Try deleting the workspace and re-trigger the build, or change the check-out strategy to 'Always check out a fresh copy'.
I faced the same problem when upgraded to 1.417 from 1.413.
The combobox "Ant version" disappeared from "Invoke ant" build step. It should be here.
I just downgraded to 1.413 and continue to work.
So, the answer is - you should specify "Ant version" in project settings. But you cannot do it in 1.417.
It seems like Jenkins doesn't like when you create a job before configuring JDK. If that happens, job will never work properly. So, for me the solution was:
Delete job.
Configure JDK
Re-create job.
Probably the same problem may arise when job's JDK is deleted.
In my case,ant default target was not being picked up from build.xml so I had to explicitly mention the target in jenkins option.
I resolved this by changing the jdk to default and then again switched to what was set earlier.This is a workaround but not sure how this resolved.