Unable to Run Pipeline After Updating Parameter-Based Material

40 views
Skip to first unread message

Jason Smyth

unread,
Dec 6, 2019, 6:16:14 PM12/6/19
to go-cd
Hello,

We have a GoCD Pipeline that depends on a version-controlled zip archive as one of its materials. To mitigate space issues caused by versioning a large binary file, the zip archive is rotated monthly. The upstream process that commits the archive timestamps it with YYYY-MM and every month we update a Parameter on our GoCD Pipeline to ensure we pull the latest file.

This has been working fine for the past 2+ years but this month GoCD started throwing errors as soon as we update the Parameter to the current date. The error message we are seeing is:

No row with the given identifier exists: [com.thoughtworks.go.domain.MaterialInstance#124725]; nested exception is org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [com.thoughtworks.go.domain.MaterialInstance#124725]

As a result of this error:
In case it is relevant, the source control system is TFS. The Parameter is used in the Material's Project Path ($/MyTeamProject/#{zipFile}) and Destination Directory (zipFile\#{zipFile}).

As noted above, the errors start as soon as we change the date pattern in the zipFile Parameter from 2019-11 to 2019-12. When we revert from 2019-12 back to 2019-11 they clear again. We have a test server that is a clone of our production server and this Pipeline works fine in dev.

Any thoughts on what we can do to resolve this issue?

Any help is appreciated.

Thank you,
Jason

Aravind SV

unread,
Dec 9, 2019, 8:58:40 AM12/9/19
to go...@googlegroups.com
Hello Jason,

It might be best to open an issue on GitHub with more snippets from the log, or the whole log itself.

Cheers,
Aravind

On Fri, Dec 06, 2019 at 15:16:14 -0800, Jason Smyth wrote:
> Hello,
>
> We have a GoCD Pipeline that depends on a version-controlled zip archive as
> one of its materials. To mitigate space issues caused by versioning a large
> binary file, the zip archive is rotated monthly. The upstream process that
> commits the archive timestamps it with YYYY-MM and every month we update a
> Parameter on our GoCD Pipeline to ensure we pull the latest file.
>
> This has been working fine for the past 2+ years but this month GoCD
> started throwing errors as soon as we update the Parameter to the current
> date. The error message we are seeing is:
>
> No row with the given identifier exists:
> [com.thoughtworks.go.domain.MaterialInstance#124725]; nested exception is
> org.hibernate.ObjectNotFoundException: No row with the given identifier
> exists: [com.thoughtworks.go.domain.MaterialInstance#124725]
>
> As a result of this error:
>
> - GoCD fails when checking for a modification to the Material (error as
> above).
> - GoCD fails to schedule the Pipeline (error as above).
> - GoCD fails to display Pipeline History in the UI
> (http://gocd:8153/go/pipelineHistory.json?pipelineName=<affectedPipeline>
> returns HTTP 500).
> - GoCD succeeds to display Pipeline History in the API

Jason Smyth

unread,
Dec 10, 2019, 11:37:30 AM12/10/19
to go-cd
Thank you for the reply, Aravind.

Although I could consistently reproduce this issue on Friday, as of just now I am unable to and the Pipeline runs normally when I change the parameter to support the current month.

I guess the issue resolved itself.

Cheers,
Jason
Reply all
Reply to author
Forward
0 new messages