Just noticed i fixed the validate call, but its failing for normal calls due to additional function support needed. Patch coming soon
Another thought that i didn't do in the MR above.
Would be to add it to the /admin/reports/updates page as a new tab or extend of the settings tab.
Similar to
- /admin/reports/updates
- admin/reports/updates/update
- /admin/reports/updates/settings
Idea 1 : add to /admin/reports/updates/settings page as additional form items.
Idea 2: add new tab like /admin/reports/updates/jira_updates_drupal
Idea 3: which i did above in the MR. Add it to the /admin/config/services/jira_updates_reporter
dan kolbas → created an issue.
I agree that this should be updated. I just tossed together some code to help assist with this. Most of the bulk changes were done to the provider form.
WHY
I have an initiative at my work to build out a custom gitlab pipeline that will integrate JIRA_REST and atm i am leaning towards jira_updates_reporter module. So that we can automate our process for keeping our contributed modules updated with the least amount of effort.
Aka.
- Create JIRA tickets based on modules out of date based on druapl.org
- spin up containerized preview environments with an MR against our projects with the update applied.
- run our regression tests, performance tests against it and update jira accordingly.
- In turn triggering it to be passed it off to our QA team if nothing goes wrong.
Take out that developer intervention. ;)
I mention the above because the updates here and to the jira_updates_reporter are planed to be generic enough that people using this might be interested as well in it when i am done.
dan kolbas → made their first commit to this issue’s fork.
Dan Kolbas → made their first commit to this issue’s fork.
Moving into Review state.
Dan Kolbas → created an issue.
Patch and MR created.
- Passed testing as well.
Opening this up for Review.
Dan Kolbas → created an issue.
Dan Kolbas → created an issue.