Yes they would be resolved assuming you've automatic polling enabled for
the material or if you've manually triggered the pipeline that depend
directly on this material.

AFAIK, GoCD maintains the commit SHA it has seen for every material as it
flows through the pipelines. For a variety of reasons the SHA could go away
(rebase and force push are the ones I've seen in my org) from the repo.
When trying to schedule the pipeline that depend on this material and SHA
version, if GoCD can't find it - IMHO it should ideally bomb saying
something is wrong - which is what it's doing.

On Fri, Sep 23, 2016 at 2:04 AM, Brian Beggs <bbe...@edx.org> wrote:

> Ashwanth very Interesting. We do a lot of rebasing and force pushing
> though typically not to the master branch of the repository. Once this
> merge came in to master there have been 5 or 6 PRs merged on to master. If
> I understand what you are saying correctly the issue should have been
> cleared up once those PRs were merged?
>
> FWIW I do not believe that this is due to changing of the material as it
> has not changed.
>
> This sounds like a defect in in GoCD, any idea if there is a ticket open
> to deal with this?
>
> Thanks,
>
> Brian
>
> On Thursday, September 22, 2016 at 3:22:28 PM UTC-4, Aravind SV wrote:
>>
>> It could also happen if you change the configuration of the material (in
>> case you point it to a different repo, for instance). That can cause it to
>> be seen as a new material and the old commits (and hence the SHAs) won't
>> show up in the autocomplete. As a rule, if it doesn't show up in the
>> dropdown, it won't be allowed to be built (you'll see the error you saw
>> there).
>>
>> On Thu, Sep 22, 2016 at 2:59 PM, 'Ashwanth Kumar' via go-cd <
>> go...@googlegroups.com> wrote:
>>
>>> Brian,
>>>
>>> This generally happens when you force-push or rebase (aka rewrite git
>>> history) on a branch. You can fix this, if would make another commit on the
>>> respective branch of the repo.
>>>
>>>
>>> On Fri, Sep 23, 2016 at 12:12 AM, Brian Beggs <bbe...@edx.org> wrote:
>>>
>>>> I should also mention that we are running gocd 16.5.0. (and fix up the
>>>> subject line)
>>>>
>>>> On Thursday, September 22, 2016 at 2:32:21 PM UTC-4, Brian Beggs wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>>
>>>>> I am seeing some strange behavior with GoCD. We are trying to run a
>>>>> pipeline with a specific git revision 
>>>>> (7bf17ab3ff980fa691d946cacf7f4fdb09a90809),
>>>>> though when I go to the UI and search for this sha for the material,
>>>>> nothing comes up. I did some digging and it looks like other than the last
>>>>> 15ish commits (about 10 days worth of work) no longer show up in the UI 
>>>>> and
>>>>> we are unable to build with them even when entering the exact sha.
>>>>>
>>>>>
>>>>> I have pulled the following out of the logs:
>>>>>
>>>>> 2016-09-22 18:19:39,307 ERROR [59@MessageListener for
>>>>> MaterialUpdateStatusNotifier] BuildCauseProducerService:248 - Error while
>>>>> scheduling pipeline: loadtest-edx-ecommerce
>>>>>
>>>>> java.lang.RuntimeException: Unable to find revision
>>>>> [7bf17ab3ff980fa691d946cacf7f4fdb09a90809] for material
>>>>> [GitMaterial{url=https://github.com/edx/ecommerce.git,
>>>>> branch='master', submoduleFolder='null', shallowClone=false}]
>>>>>
>>>>>         at com.thoughtworks.go.server.mat
>>>>> erials.MaterialChecker.findSpecificRevision(MaterialChecker.java:52)
>>>>>
>>>>>         at com.thoughtworks.go.server.mat
>>>>> erials.SpecificMaterialRevisionFactory.create(SpecificMateri
>>>>> alRevisionFactory.java:53)
>>>>>
>>>>>         at com.thoughtworks.go.server.sch
>>>>> eduling.BuildCauseProducerService.newProduceBuildCause(Build
>>>>> CauseProducerService.java:177)
>>>>>
>>>>>         at com.thoughtworks.go.server.sch
>>>>> eduling.BuildCauseProducerService$WaitForPipelineMaterialUpd
>>>>> ate.onMaterialUpdate(BuildCauseProducerService.java:416)
>>>>>
>>>>>         at com.thoughtworks.go.server.mat
>>>>> erials.MaterialUpdateStatusNotifier.onMessage(MaterialUpdate
>>>>> StatusNotifier.java:55)
>>>>>
>>>>>         at com.thoughtworks.go.server.mat
>>>>> erials.MaterialUpdateStatusNotifier.onMessage(MaterialUpdate
>>>>> StatusNotifier.java:29)
>>>>>
>>>>>         at com.thoughtworks.go.server.mes
>>>>> saging.activemq.JMSMessageListenerAdapter.runImpl(JMSMessage
>>>>> ListenerAdapter.java:65)
>>>>>
>>>>>         at com.thoughtworks.go.server.mes
>>>>> saging.activemq.JMSMessageListenerAdapter.run(JMSMessageList
>>>>> enerAdapter.java:50)
>>>>>
>>>>>         at java.lang.Thread.run(Thread.java:745)
>>>>>
>>>>>
>>>>> And here is a link to the commit history of the project:
>>>>> https://github.com/edx/ecommerce/commits/master
>>>>>
>>>>>
>>>>> Any Idea what is going on here? Should I expect to see this sha in the
>>>>> list?
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>>
>>>>> Brian
>>>>>
>>>>>
>>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "go-cd" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to go-cd+un...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Ashwanth Kumar / ashwanthkumar.in
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "go-cd" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to go-cd+un...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Ashwanth Kumar / ashwanthkumar.in

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to