[INFRA-105] JIRA Components for INSTRM project Created: 04/Jan/17  Updated: 17/Apr/17  Resolved: 17/Apr/17

Status: Done
Project: Software Development Infrastructure
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: cloomis Assignee: shimono
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Have we gotten rid of Components? When creating an issue, the Component/s field is fixed as None.

For ICS they would be quite useful: there are enough actors/sub-components that we'd like to be able to partition/tag issues.

 Comments   
Comment by shimono [ 04/Jan/17 ]

Yes. Please propose names of component you need. Add here (initial list until marked as done) or file an individual ticket.

Comment by cloomis [ 04/Jan/17 ]

What happened to the old ones? Can't we just add them dynamically?

xcuActor, ccdActor, enuActor, xcu_fpga, actorkeys, actorcore, etc. etc. etc.

Comment by shimono [ 10/Jan/17 ]

What means by "the old ones"??
I don't know how much we can get integration plugins to github on JIRA, but something could be possible, I suppose. If you know something nice, we can consider of, of course.

We may be better to think about granularity for components (e.g. per group of functionality like multiple repos for ENU), but per github repo could be a good starting point...

Comment by cloomis [ 11/Jan/17 ]

I'm pretty sure I had added components to ICS tickets.

To start with, per-repo components would be a big help now. It is often obvious which repos need work, and their names are not ambiguous.

Comment by shimono [ 11/Jan/17 ]

Old JIRA ICS project was migrated to github and no more available at the point of migration to INSTRM project.

cloomis
just confirm, adding following components for PU/JHU part:

  • ics_xcuActor
  • ics_ccdActor
  • ics_xcu_fpga
  • ics_xcu_pcm
  • ics_xcu_fee
  • ics_xcu_rtdADIO

Also adding following components for tron:

  • ics_archiver
  • ics_coreActor
  • ics_config
  • ics_actorkeys
  • tron_tron
  • tron_actorcore

arnaud.lefur fmadec
Do you want to have one component per following each ENU repo?:

  • ics_sps_engineering_JabberBot
  • ics_sps_engineering_plotData
  • ics_sps_engineering_monitorData
  • ics_sps_engineering_Lib_dataQuery
  • ics_enuActor
  • ics_spsaitActor
  • ics_hxpActor
  • ics_rexmActor
  • ics_bshActor

chihyi sywang
Do you want to have one component per following each PFI, MCS repo?:

  • ics_agccActor
  • ics_mcsActor
  • ics_fpsActor
  • ics_fccActor
  • ics_fvcActor
  • ics_pebActor
  • ics_pfiaitActor

I will add followings (individually):

  • ics_macActor (MLP1 AG converter)
  • ics_empActor (Environment monitor for SCR)
  • ics_dnsmasq
  • ics_doc
Comment by cloomis [ 13/Jan/17 ]

I would be happy with that list.

Comment by shimono [ 16/Jan/17 ]
  • added components for xCU, tron, and IPMU ones
  • added components for system side: doc, dnsmasq, and summit-infrastructure
Comment by fmadec [ 02/Feb/17 ]

the list you proposed is fine for me

Comment by shimono [ 06/Feb/17 ]

fmadec arnaud.lefur added.

Comment by cloomis [ 17/Feb/17 ]

Can you add an "ics_hxActor", please? I do have a repo, but would prefer not to move it into the Subaru-PFS space just yet.

Comment by shimono [ 17/Feb/17 ]

Added. but do we really want to track things here for hxActor?

Comment by cloomis [ 17/Feb/17 ]

Thanks.

This is for the actor side, not the hxhal side. That said, I'll probably add hxhal tickets as well, but will not add details.

Comment by chihyi [ 17/Apr/17 ]

Atshushi, could you add the components that you proposed? Sorry for late response.

Comment by shimono [ 17/Apr/17 ]

All added for proposed subsystems (and components).

> chihyi
Please check ones for PFI.

Generated at Sat Feb 10 16:49:28 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.