[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Tom FENNELLY commented on JENKINS-39794 Re: API to check that MBP indexing has completed Changes for the new event data are now pushed upstream. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Tom FENNELLY updated JENKINS-39794 Jenkins / JENKINS-39794 API to check that MBP indexing has completed Change By: Tom FENNELLY Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Tom FENNELLY updated JENKINS-39794 Jenkins / JENKINS-39794 API to check that MBP indexing has completed Change By: Tom FENNELLY Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39794 API to check that MBP indexing has completed Change By: James Dumay Sprint: tasman, frank, tethys, christmas , pannonian Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Tom FENNELLY commented on JENKINS-39794 Re: API to check that MBP indexing has completed Cliff Meyers and I spent some time yesterday investigating the pipeline API looking for a way to get what he needs and we think we found something that will cover at least the normal MBP indexing requirements i.e. sending an "indexing complete with success/fail status" even at the right time. I should have a prototype that he can test later. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Tom FENNELLY commented on JENKINS-39794 Re: API to check that MBP indexing has completed Experiments under way with Cliff. Waiting for feedback on https://github.com/jenkinsci/blueocean-plugin/pull/700 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Tom FENNELLY commented on JENKINS-39794 Re: API to check that MBP indexing has completed Actually looks easy enough ... requires an addition to the pubsub module. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Tom FENNELLY commented on JENKINS-39794 Re: API to check that MBP indexing has completed Cliff Meyers So I guess we need to find out what's available in pipeline (or one of its sub plugins) that we can use to trigger the publishing of these events on the pubsub bus. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Tom FENNELLY started work on JENKINS-39794 Change By: Tom FENNELLY Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Cliff Meyers commented on JENKINS-39794 Re: API to check that MBP indexing has completed Tom FENNELLY you're right, it doesn't (and probably shouldn't) be specified to Github. It could probably be basic events about "indexing started" and "indexing completed", perhaps with some additional metadata that could express the type of the thing that was indexing? If we have HAL href's the UI might very well be ignore the types anyways and just compare based off href, but other consumers might need some kind of type info. For errors, that would be fine. If I recall, a job "completes" but has a state of failed, success ,etc? If so, probably good to follow that Jenkins convention. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Tom FENNELLY commented on JENKINS-39794 Re: API to check that MBP indexing has completed Cliff Meyers Would it be possible to have more generic events for "Github org folder started" etc? Otherwise I'd like us to drill into why it needs to be explicit to Github so I can get a better idea. As for errors etc ... can that kind of thing not be a status/result on the end event ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Vivek Pandey commented on JENKINS-39794 Re: API to check that MBP indexing has completed Cliff Meyers This kind of validation can be done, like given git url is valid git or not. Please note, even if its valid URL, indexing might succeed with no branch as there may not be any Jenkinsfile. You are right an event to indicate any valid pipeline branch is found or no pipeline found might help. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Cliff Meyers commented on JENKINS-39794 Re: API to check that MBP indexing has completed Also potentially related to this, cc Michael Neale Vivek Pandey I noticed that if I create a new Git project based off a bogus URL (e.g. http://www.foo) that creation immediately returns with success. I understand the API constraints and why it needs to create it immediately, but it feels like we need to let Jenkins to do a little work first and give the user some kind of indication that something went wrong? If that's the case, then maybe we need some other kind of event that indicates an indexing failure, or that indexing didn't find anything useful? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Cliff Meyers commented on JENKINS-39794 Re: API to check that MBP indexing has completed Tom FENNELLY for context I would check out these two links: Github Creation Flow, especially steps 7-9: https://cloudbees.atlassian.net/wiki/display/UX/Pipeline+Creation#PipelineCreation-ConnectingtoGithub.com Git Creation flow, steps 2.1 and 2.2: https://cloudbees.atlassian.net/wiki/display/UX/Pipeline+Creation#PipelineCreation-Git So once the user presses the create button, the UI will call the backend API to begin creation, but that really only begins the process. Jenkins has saved and created the folder or pipeline, but it hasn't been indexed yet, so the data is just an empty shell, and navigating to any page in the UI at this moment isn't going to show anything useful. The UI will stay in the creation UI for a bit while "the system is working" and then perform some navigation to an appropriate page at the right time: When creating a Github org folder a.k.a. "auto discover": the UI should stay in the creation flow until all of the pipelines for that org have been created. This is the concept we've been discussing of getting events for when an org folder's indexing starts and completes. I suspect the progress indicator at the bottom would move through these states: (making API call to begin creation) - "Saving Changes..." (after API calls completes) - "Waiting for Indexing..." (after receiving "indexing started" event) - "Creating Pipelines" (after receiving "indexing complete" event) - "Pipelines Created!" - navigate back to Dashboard, show the pipelines that were created. If the UI could make a REST API call to fetch additional data about the Github Org folder (for example, the names of the pipelines in it, similar to a MBP's "branchNames" property) then we could show some cool info like "22 Pipelines Created!" When creating a single repo (either from Github or Git flow), it's not an org folder indexing that's relevant, but the indexing of a specific multibranch pipeline. The progress indicator would have these states... (making API call to begin creation) - "Saving Changes..." (after API calls completes) - "Waiting for Indexing..." (after receiving "indexing started" event) - "Creating Pipeline" (after receiving "indexing complete" event) - "Pipeline Created!" - navigate to /activity tab for that pipeline For 2.4, we might eventually smarten it up a bit to navigate either to editor or to in-progress run if the repo had a Jenkinsfile but I don't think that really relates to any of the eventing we're talking about here, just an FYI. So to summarize, perhaps this would serve
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title
Tom FENNELLY commented on JENKINS-39794
Re: API to check that MBP indexing has completed
Michael Neale Cliff Meyers I'll lend a hand as best I can as soon as someone adds some high level details on what this is about, as requested a few times above. E.g.
What's the higher level use case ("We want the user to be able to see when ... etc etc") ? + maybe a screenshot mockup if we have any.
What specific events do we think we need fired on the bus on the backend?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Michael Neale edited a comment on JENKINS-39794 Re: API to check that MBP indexing has completed [~cliffmeyers] yes, we want to show it is busy, until it isn't. Once it has finished, then the final state can be displayed unless there was an error (vivek says that the api can tell you if it is finished with an error or not) . If there was an error, we should show it (I doubt it will be a very nice error, but we will see. With github 90% of the time is permission so we should capture that before setting it up. The reminaining 9.99% is usually API rate limiting or network, and that should be helped by the update to the SCM api and plugins next week. An SSE event will make this work nicely in theory... [~tfennelly] you able to help vivek and cliff here? we might need some more hooks to get MBP and perhaps github org folder events published to the SSE bus, as there doesn't appear to be anything there (may not even be listeners) just yet. Cliff needs to know that a given pipeline has finished indexing at least (and in the case of github org folder scanning for repos, that it has finished). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Michael Neale assigned an issue to Tom FENNELLY Jenkins / JENKINS-39794 API to check that MBP indexing has completed Change By: Michael Neale Assignee: Vivek Pandey Tom FENNELLY Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Michael Neale commented on JENKINS-39794 Re: API to check that MBP indexing has completed Cliff Meyers yes, we want to show it is busy, until it isn't. Once it has finished, then the final state can be displayed unless there was an error. If there was an error, we should show it (I doubt it will be a very nice error, but we will see. With github 90% of the time is permission so we should capture that before setting it up. The reminaining 9.99% is usually API rate limiting or network, and that should be helped by the update to the SCM api and plugins next week. Tom FENNELLY you able to help vivek and cliff here? we might need some more hooks to get MBP and perhaps github org folder events published to the SSE bus, as there doesn't appear to be anything there (may not even be listeners) just yet. Cliff needs to know that a given pipeline has finished indexing at least (and in the case of github org folder scanning for repos, that it has finished). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Michael Neale stopped work on JENKINS-39794 Change By: Michael Neale Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay commented on JENKINS-39794 Re: API to check that MBP indexing has completed That's right Cliff. I think it would be good to know if the indexing stopped with an error or success too. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Cliff Meyers commented on JENKINS-39794 Re: API to check that MBP indexing has completed James Dumay Brody Maclean would help to have some input from product and UX here. After the user creates a Github org folder, what kind of feedback are we going to show at the bottom to illustrate the progress? Are we going to wait until indexing of the org folder is complete to navigate the user back to dashboard? If so we probably just need to know that the org folder's indexing started and stopped. If we are going to show something more detailed to the user, then we would need more granular events. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39794 API to check that MBP indexing has completed Change By: James Dumay Priority: Blocker Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay commented on JENKINS-39794 Re: API to check that MBP indexing has completed Blocking Cliffs Creation epic Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39794 API to check that MBP indexing has completed Change By: James Dumay Priority: Minor Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39794 API to check that MBP indexing has completed Change By: James Dumay Sprint: tasman, frank, tethys, christmas Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Vivek Pandey commented on JENKINS-39794 Re: API to check that MBP indexing has completed James Dumay Other day Cliff Meyers mentioned, he cares about org scan events, begin and end. Cliff, is that it? Tom FENNELLY wants some description of it, like high level use case. Cliff Meyers can you sync up your morning with Tom? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay commented on JENKINS-39794 Re: API to check that MBP indexing has completed Vivek Pandey best catch up with Cliff Meyers and see what he prefers to determine MBP/Org folder indexing status. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Vivek Pandey commented on JENKINS-39794 Re: API to check that MBP indexing has completed James Dumay See above comments, please add more details to it so that its clear where/what needs to be done. For one I think intent is to send events for org scan and not MBP indexing or maybe both. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Tom FENNELLY commented on JENKINS-39794 Re: API to check that MBP indexing has completed But first ... lets please describe what we are trying to do from a higher level. Then we can figure out what we need or if there's a bug. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Tom FENNELLY commented on JENKINS-39794 Re: API to check that MBP indexing has completed Vivek Pandey Hey Vivek ... the network tab is not going to tell you anything useful here. You need to turn on the SSE event logging in order to see the events coming through to the client. What I would expect is that you'd see job_crud_created events being logged to the console (among other things). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Vivek Pandey commented on JENKINS-39794 Re: API to check that MBP indexing has completed Tom FENNELLY James Dumay can provide more details but from what I understand basically we need SSE events for start and stop of indexing so that UI can show indexing status. So I tried it on BO master branch and triggering indexing of MBP is not resulting in to an SSE events, that is by looking in to chrome networking req/resp. I suspect BranchIndexing.run() basically FolderComputation.run() is not firing off RunListener.fireStarted() or other events. On blueocean side of things look ok, SSEService.js is subscribing to job channel and accepting all events. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Vivek Pandey started work on JENKINS-39794 Change By: Vivek Pandey Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title Tom FENNELLY commented on JENKINS-39794 Re: API to check that MBP indexing has completed Need to add SSE events for start and stop of indexing An SSE event or a REST API? They seem like 2 different things in how they are described. Maybe the description is just wrong. Also, maybe a bit more detail on the problem that we're trying to solve. AFAIK, MBP indexing results in SSE events when new pipeline jobs are created etc. Is there a bug with that (not created or not consumed), or is something else needed? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39794 API to check that MBP indexing has completed Change By: James Dumay Sprint: tasman, frank , christmas Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39794 API to check that MBP indexing has completed Change By: James Dumay Sprint: tasman, tethys frank Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39794 API to check that MBP indexing has completed Change By: James Dumay Sprint: tasman, frank tethys Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39794 API to check that MBP indexing has completed Change By: James Dumay Sprint: tasman , frank Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay assigned an issue to Vivek Pandey Jenkins / JENKINS-39794 API to check that MBP indexing has completed Change By: James Dumay Assignee: Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39794 API to check that MBP indexing has completed Change By: James Dumay Sprint: tasman Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay commented on JENKINS-39794 Re: API to check that MBP indexing has completed Need to add SSE events for start and stop of indexing Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay created an issue Jenkins / JENKINS-39794 API to check that MBP indexing has completed Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/16 9:48 PM Priority: Minor Reporter: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins
