Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: delivery-pipeline-plugin
-
Labels:None
-
Environment:Cloudbees Jenkins
-
Similar Issues:
Description
Job & View Folder Structure:
RootFolder/
--Continous Delivery View
--SubFolder/
----JobA
----JobB
JobA -> (Manual Trigger) -> JobB
If the delivery pipeline view is created at a different folder level than where the manually triggered job is located, it throws a null pointer exception.
I've tried multiple combinations of specifying the absolute path, relative path from the view but, it will not take.
The relative path from the view would probably work to trigger the manual job from the view but it does not display the manual job in the CD view because when it reads the trigger chain specified in the job config, the job folder location is incorrect.
Attachments
Activity
Ferzan Rizvi
created issue -
Ferzan Rizvi
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
Job & View Folder Structure: RootFolder/ CD View SubFolder/ JobA-Initial JobB-Manual JobA-Initial -> (Manual Trigger) -> JobB-Manual If the delivery pipeline view is created at a different folder level than where the manually triggered job is located, it throws a null pointer exception. I've tried multiple combinations of specifying the absolute path, relative path from the view but, it will not take. The relative path from the view would probably work to manually trigger the job from the view but it does not display the job in pipeline view because when it reads the trigger chain specified in the jobs, the job folder location will be incorrect. |
Job & View Folder Structure: RootFolder/ --Continous Delivery View --SubFolder/ ----JobA-Initial ----JobB-Manual JobA-Initial -> (Manual Trigger) -> JobB-Manual If the delivery pipeline view is created at a different folder level than where the manually triggered job is located, it throws a null pointer exception. I've tried multiple combinations of specifying the absolute path, relative path from the view but, it will not take. The relative path from the view would probably work to manually trigger the job from the view but it does not display the job in pipeline view because when it reads the trigger chain specified in the jobs, the job folder location will be incorrect. |
Ferzan Rizvi
made changes -
| Description |
Job & View Folder Structure: RootFolder/ --Continous Delivery View --SubFolder/ ----JobA-Initial ----JobB-Manual JobA-Initial -> (Manual Trigger) -> JobB-Manual If the delivery pipeline view is created at a different folder level than where the manually triggered job is located, it throws a null pointer exception. I've tried multiple combinations of specifying the absolute path, relative path from the view but, it will not take. The relative path from the view would probably work to manually trigger the job from the view but it does not display the job in pipeline view because when it reads the trigger chain specified in the jobs, the job folder location will be incorrect. |
Job & View Folder Structure: RootFolder/ --Continous Delivery View --SubFolder/ ----JobA-Initial ----JobB-Manual JobA-Initial -> (Manual Trigger) -> JobB-Manual If the delivery pipeline view is created at a different folder level than where the manually triggered job is located, it throws a null pointer exception. I've tried multiple combinations of specifying the absolute path, relative path from the view but, it will not take. The relative path from the view would probably work to manually trigger the job from the view but it does not display the job in pipeline view because when it reads the trigger chain specified in the jobs, the job folder location will be incorrect. |
Ferzan Rizvi
made changes -
| Description |
Job & View Folder Structure: RootFolder/ --Continous Delivery View --SubFolder/ ----JobA-Initial ----JobB-Manual JobA-Initial -> (Manual Trigger) -> JobB-Manual If the delivery pipeline view is created at a different folder level than where the manually triggered job is located, it throws a null pointer exception. I've tried multiple combinations of specifying the absolute path, relative path from the view but, it will not take. The relative path from the view would probably work to manually trigger the job from the view but it does not display the job in pipeline view because when it reads the trigger chain specified in the jobs, the job folder location will be incorrect. |
Job & View Folder Structure: RootFolder/ --Continous Delivery View --SubFolder/ ----JobA-Initial ----JobB-Manual JobA-Initial -> (Manual Trigger) -> JobB-Manual If the delivery pipeline view is created at a different folder level than where the manually triggered job is located, it throws a null pointer exception. I've tried multiple combinations of specifying the absolute path, relative path from the view but, it will not take. The relative path from the view would probably work to manually trigger the job from the view but it does not display the job in the CD view because when it reads the trigger chain specified in the job config, the job folder location will be incorrect. |
Ferzan Rizvi
made changes -
| Description |
Job & View Folder Structure: RootFolder/ --Continous Delivery View --SubFolder/ ----JobA-Initial ----JobB-Manual JobA-Initial -> (Manual Trigger) -> JobB-Manual If the delivery pipeline view is created at a different folder level than where the manually triggered job is located, it throws a null pointer exception. I've tried multiple combinations of specifying the absolute path, relative path from the view but, it will not take. The relative path from the view would probably work to manually trigger the job from the view but it does not display the job in the CD view because when it reads the trigger chain specified in the job config, the job folder location will be incorrect. |
Job & View Folder Structure: RootFolder/ --Continous Delivery View --SubFolder/ ----JobA-Initial ----JobB-Manual JobA-Initial -> (Manual Trigger) -> JobB-Manual If the delivery pipeline view is created at a different folder level than where the manually triggered job is located, it throws a null pointer exception. I've tried multiple combinations of specifying the absolute path, relative path from the view but, it will not take. The relative path from the view would probably work to trigger the manual job from the view but it does not display the manual job in the CD view because when it reads the trigger chain specified in the job config, the job folder location is incorrect. |
Ferzan Rizvi
made changes -
| Description |
Job & View Folder Structure: RootFolder/ --Continous Delivery View --SubFolder/ ----JobA-Initial ----JobB-Manual JobA-Initial -> (Manual Trigger) -> JobB-Manual If the delivery pipeline view is created at a different folder level than where the manually triggered job is located, it throws a null pointer exception. I've tried multiple combinations of specifying the absolute path, relative path from the view but, it will not take. The relative path from the view would probably work to trigger the manual job from the view but it does not display the manual job in the CD view because when it reads the trigger chain specified in the job config, the job folder location is incorrect. |
Job & View Folder Structure: RootFolder/ --Continous Delivery View --SubFolder/ ----JobA ----JobB JobA -> (Manual Trigger) -> JobB If the delivery pipeline view is created at a different folder level than where the manually triggered job is located, it throws a null pointer exception. I've tried multiple combinations of specifying the absolute path, relative path from the view but, it will not take. The relative path from the view would probably work to trigger the manual job from the view but it does not display the manual job in the CD view because when it reads the trigger chain specified in the job config, the job folder location is incorrect. |
Ferzan Rizvi
made changes -
| Attachment | StackTrace.txt [ 26644 ] |
| Assignee | Patrik Boström [ patbos ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Workflow | JNJira [ 157315 ] | JNJira + In-Review [ 207988 ] |