Anyone have an idea why my workflow job is showing "Average full run time: ~45y 358d"? I imagine it has something to do with a timestamp?
It's a known bug in the CloudBees proprietary plugin cloudbees-workflow-plugin. Not fixed yet.
Related
Ugh....Microsoft have done something.
All our builds that have been kicked off in the last few hours (approx 10:00 GMT) are failing on our "Build Solution step" failing because of the following error (from the logs):
##[error]EXEC(0,0): Error : Error occurred during processing of input file 'XXX.XXX.dll' --> Method not found: 'System.ReadOnlySpan1 Microsoft.IO.Path.GetFileName(System.ReadOnlySpan1<Char>)'.
Does anyone have any ideas on this? Nothing in our codebase has changed.
If you need more information please let me know. Thanks
FYI, this seems to be caused by a recent update to MSBuild (https://github.com/dotnet/msbuild/pull/7680) that has updated the version of System.Memory.
It looks like the obfuscation tool you're using in your build pipeline is built against a previous version of System.Memory and now that the version provided by the MSBuild environment has changed, the obfuscation tool is broken. Most likely requires the obfuscation tool to be updated.
(PS. I'm just relaying the information that others have identified where other tools are having the same issue - see https://github.com/T4MVC/R4MVC/issues/172)
Back in 2014 Enthought's build of GDAL/OGR was missing important functionality. In October of that year John from Enthought wrote:
"Correct, there are many possible build configurations of GDAL/OGR, and geos is not currently supported by Enthought's build configuration. We will consider adding it in a future build. "
Did this happen? For example, can we now use OGR's buffer method?
Sorry, not yet, not much apparent demand relative to other packages.
Reference:
https://stackoverflow.com/a/26596496/1988991
Since 2 days we have a really big issue on our TFS system.
After the build agent activity the build stay stuck undefinitely.
We have detected that the issue is linked to the NotifyBuildCompleted action in the closure part of the build event.
A timeout occured each time this part of the build process is reached.
At the end the build agent is available but the build controler is still busy with the closure and will not see anymore the agent as available.
On the Build overview panel I can see the build is still "In Process" and also it's in the completed tab . The duration, completed date and execution time have bad values. In the database the tbl_buildqueued stay with the build status 1 instead of the closed status.
We have CI build since 1 month and it's the first time we have this kind of issue.
Did someone have a solution or an idea to solve this issue ?
Run the BPA which can be downloaded from here and see if there are any issues with the accounts that are used for TFS, particularly the SQL and sharepoint accounts
After weeks of search and contact with microsoft it's something linked to the stored procedure.
To avoid this build stuck we add 1 GO memory on our SQL server .
Now build are correctly stoped / finished by the NotificationCompleted event.
Regards
I have setup the trigger to listen to the last pinned build artifacts:
<TEAMCITY URL>/repository/downloadAll/bt79/.lastPinned
However, the trigger keeps firing every 30 seconds which is the default Polling interval.
Am I missing something here? The url always gives me the same file.
UPDATE:
After upgrading to TeamCity 7.1 the problem still exists.
The answer to this question came from TeamCity support:
The reason of the described behaviour is the way TeamCity controller
returns data requested in downloadAll query. The .zip containing the
artifacts is actually different on each request and build is
triggered.
To workaround this issue try using
<TEAMCITY URL>/guestAuth/repository/download/bt79/.lastPinned/<some artifact> if possible.
this one worked for me.
every morning when i come to work i update my sources from the svn and build it. this process takes roughly 15 min.
my question is whether it is possible to do it automatically, scheduling it...
i am working with XP and eclipse.
As John mentions in the comments, setting up an Hudson server is the quickest way to schedule this kind of task: