Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: batch-task-plugin
    • Labels:
      None
    • Environment:
      Hudson 1.344, Hudson batch task plugin 1.12
    • Similar Issues:

      Description

      "Task" menu isn't shown in the job's left menu, if there aren't tasks defined but in the current job's configuration, but there are tasks configured for execution in job's configuration using other job's tasks.

      "Task" Menu should always be visible if there are tasks being used by current job's configuration, even if it's not it's own tasks.

      Thanks in advance.

        Attachments

          Activity

          Hide
          mindless Alan Harder added a comment -

          I don't see a bug here.. it shows the sidepanel link if this job has any tasks. Whether or not the job invokes batch tasks from other jobs as a post-build action is not a factor here. Can we close this issue?

          Show
          mindless Alan Harder added a comment - I don't see a bug here.. it shows the sidepanel link if this job has any tasks. Whether or not the job invokes batch tasks from other jobs as a post-build action is not a factor here. Can we close this issue?
          Hide
          hmonteiro hmonteiro added a comment -

          I understand what you are saying.
          So, how can we run batch tasks used by this job, tasks created not in this job but in other jobs), if the menu is not visible?

          In my opinion, I was expecting that the tasks menu be always be visible everytime there is a task configured in the current job or everytime that that job has a post-build task defined (even if it's not its own).

          The real issue I came across, that forward me to open this ticket is : How can I manually run an "external" task defined to run in the current job, if there is no menu for it (they only appear when the current job has them defined)?

          An idea I have to resolve this issue, would be to completly disable usage of external tasks altogether (you can trigger other job's afterall).

          Here's an idea to simplify the tasks configuration:

          • move the "Batch tasks" section in jobs configuration down to where "Invoke batch tasks" section currently exists; (I think this would also solve ticket #5580)
          • add an additional field called "Enabled" to every task. So the task could be configured to run or not;
          • Add ability to organize tasks order of execution (move them up and down in list, so they are executed in order they appear);
          • remove "Invoke batch tasks" section altogether, so only tasks defined in the current job can be used. That way it becomes impossible to use other job's tasks and the menu will correctly appear when the current job has tasks defined or not (current behaviour).

          I think this last idea would solve the trouble that we (Me and some colleagues at work) are having in understanding how tasks should correctly be used.
          I think this idea would simplify the tasks definition and usage.

          Let me know if you like this idea and if this ticket should be closed and an "Improvement" or "Feature" should be opened instead.

          Thanks for your time with this.

          Show
          hmonteiro hmonteiro added a comment - I understand what you are saying. So, how can we run batch tasks used by this job, tasks created not in this job but in other jobs), if the menu is not visible? In my opinion, I was expecting that the tasks menu be always be visible everytime there is a task configured in the current job or everytime that that job has a post-build task defined (even if it's not its own). The real issue I came across, that forward me to open this ticket is : How can I manually run an "external" task defined to run in the current job, if there is no menu for it (they only appear when the current job has them defined)? An idea I have to resolve this issue, would be to completly disable usage of external tasks altogether (you can trigger other job's afterall). Here's an idea to simplify the tasks configuration: move the "Batch tasks" section in jobs configuration down to where "Invoke batch tasks" section currently exists; (I think this would also solve ticket #5580) add an additional field called "Enabled" to every task. So the task could be configured to run or not; Add ability to organize tasks order of execution (move them up and down in list, so they are executed in order they appear); remove "Invoke batch tasks" section altogether, so only tasks defined in the current job can be used. That way it becomes impossible to use other job's tasks and the menu will correctly appear when the current job has tasks defined or not (current behaviour). I think this last idea would solve the trouble that we (Me and some colleagues at work) are having in understanding how tasks should correctly be used. I think this idea would simplify the tasks definition and usage. Let me know if you like this idea and if this ticket should be closed and an "Improvement" or "Feature" should be opened instead. Thanks for your time with this.
          Hide
          mindless Alan Harder added a comment -

          Sounds to me like you want a "Downstream Tasks" section on the job page, like there is currently a "Downstream Projects" list. I'm pretty sure all those changes you describe won't be done for minimal benefit, but a list of downstream tasks might be easier to add.

          Show
          mindless Alan Harder added a comment - Sounds to me like you want a "Downstream Tasks" section on the job page, like there is currently a "Downstream Projects" list. I'm pretty sure all those changes you describe won't be done for minimal benefit, but a list of downstream tasks might be easier to add.
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in hudson
          User: : mindless
          Path:
          trunk/hudson/plugins/batch-task/pom.xml
          trunk/hudson/plugins/batch-task/src/main/java/hudson/plugins/batch_task/BatchTask.java
          trunk/hudson/plugins/batch-task/src/main/java/hudson/plugins/batch_task/BatchTaskInvoker.java
          trunk/hudson/plugins/batch-task/src/main/java/hudson/plugins/batch_task/BatchTaskProperty.java
          trunk/hudson/plugins/batch-task/src/main/java/hudson/plugins/batch_task/DownstreamTasksAction.java
          trunk/hudson/plugins/batch-task/src/main/resources/hudson/plugins/batch_task/DownstreamTasksAction/jobMain.jelly
          http://jenkins-ci.org/commit/27264
          Log:
          [batch-task] [FIXED JENKINS-5582] Show links to downstream tasks on project page

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : mindless Path: trunk/hudson/plugins/batch-task/pom.xml trunk/hudson/plugins/batch-task/src/main/java/hudson/plugins/batch_task/BatchTask.java trunk/hudson/plugins/batch-task/src/main/java/hudson/plugins/batch_task/BatchTaskInvoker.java trunk/hudson/plugins/batch-task/src/main/java/hudson/plugins/batch_task/BatchTaskProperty.java trunk/hudson/plugins/batch-task/src/main/java/hudson/plugins/batch_task/DownstreamTasksAction.java trunk/hudson/plugins/batch-task/src/main/resources/hudson/plugins/batch_task/DownstreamTasksAction/jobMain.jelly http://jenkins-ci.org/commit/27264 Log: [batch-task] [FIXED JENKINS-5582] Show links to downstream tasks on project page

            People

            • Assignee:
              mindless Alan Harder
              Reporter:
              hmonteiro hmonteiro
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: