Hi all! OCC now has two groups here on the TBC due to one migrating over from the Hub when it shut down, so we're going to archive this group.
Please join and follow the original TBC group to stay in the loop on this awesome project!
The @Community Project - Ombudsman Cloud Care team is using Metecho today for a mini sprint and noticed the creation of orgs was taking longer than usual. Looking at the build list, it looks as though it was a mix of all of our feature tests and org creations linked and changes we were making ended up with a lengthy queue.
Is there a way to increase the number of running builds at a given time?
@Nick Lindberg Yes, unfortunately for now you can't use Metecho to test changes to cumulusci.yml, because it will refuse to build an org if cumulusci.yml is different from the main branch.
Add a collaborator to our GitHub and Metecho, please!
@David Glick or @David Reed or @Cori O'Brien would you please add GitHub user jgacuya to our repo so she can get into Metecho and collaborate with us?
@Michael Kolodner added to your OSC OCC repo (not the Sprint repo). In this case we needed to invite them to the overall Org first, so they'll receive an invite they'll need to accept.
Field isn't an option for conditional display filter on a LEX page?
Any @Salesforce.org System Administrators know what is happening? Working on the Case Lightning Record Page in the repo of the @Community Project - Ombudsman Cloud Care app. Trying to add a conditionally displayed component based on whether the Sailor field on case is filled or not. But the Sailor field (which IS on the page layout, IS available to me as sysadmin by FLS) does not come up in the filter choices, either directly on the field picker or on the Advanced picker. WTF??
Turns out (thanks to the MVP Slack) that you can use the Advanced picker and span through and choose the Name field on the looked up object. But that certainly isn't obvious.
OCC Workday
Hello all, this is an official reminder that we are having two half days that add up to an OCC Work Day this Thursday and Friday, 9am to noon Eastern, on this Zoom: https://us02web.zoom.us/j/84927353576
Anyone that's worked on OCC is welcome to join. We're going to work through the open Issues in the GitHub repo with the intent to finish and release version 1.3 (working branch in Metecho is here.)
Working Group Time
Hey all, in today's OCC Team meeting we decided that we'd like to get together for some worktime to get release version 1.3 out the door. We're thinking of two half days (mornings). Looking at May 20 and 21. @Nick Lindberg - would you be able to make those days?
We can spend the first day finishing up the tasks on our end, then you can swoop in on Friday to take what we've completed and wrap it into a bow for actual release!
GitHub Help Needed!
In preparation for the PMM + V4S mini sprint (register here) we are looking at using Metecho!
Metecho will also to manage our project development declaratively (for the most part). That is where are looking for support in managing the GitHub side. Here have some experience with managing branches and branch merging is needed. You don't need to be an expert and you don't need to fully know this project!
If you want to volunteer please comment below.
Hi all!
I have finish the rough drafted of the documentation of the Flow we created at the Sprint! You can read it here. I was going for speed so please read through it and edit to add more details/clarity.
Also if anyone has CCI experience please let me know. I would love to save this Flow into GitHub.
Metecho Question
As I understand it, an Epic is the branch for developing a release, within which are Tasks that are the individual work units for that release. (Correct me if I'm already off base!) Since @Community Project - Ombudsman Cloud Care has a GitHub repo, I would assume that essentially each Task should correspond to an Issue opened on GitHub. And I've set up our most recent Epic like that. Is there somewhere within Metecho to actually make a direct connection from Task to Issue, or only within the text description, as I've done?
@Michael Kolodner Good callout -- we should probably add a way to mark a task as closed/canceled, or make that happen automatically if it's connected to a PR that gets closed. At the moment I think your options are to leave it as is, or delete the task (click the gear button next to "View pull request" at upper right). Note that deleting the task will also delete its scratch org, but will not delete the branch in github.
Can't create scratch org for @Community Project - Ombudsman Cloud Care, neither in VS Code nor using Metecho. Getting this error: Could not process MDAPI response: Update of InstalledPackage npe01: Error: Mismatching versions
Stacktrace:
2021-02-10 11:59:19: ref: ef25acd4922895ca89f894c8d3c067302a758a80
2021-02-10 11:59:19: repo_name: NPSP
2021-02-10 11:59:19: repo_owner: SalesforceFoundation
2021-02-10 11:59:19: subfolder: unpackaged/pre/account_record_types
2021-02-10 11:59:19: - name: Deploy unpackaged/pre/opportunity_record_types
2021-02-10 11:59:19: ref: ef25acd4922895ca89f894c8d3c067302a758a80
2021-02-10 11:59:19: repo_name: NPSP
2021-02-10 11:59:19: repo_owner: SalesforceFoundation
2021-02-10 11:59:19: subfolder: unpackaged/pre/opportunity_record_types
2021-02-10 11:59:19: - dependencies:
2021-02-10 11:59:19: - dependencies:
2021-02-10 11:59:19: - name: Install Contacts & Organizations 3.17 (Beta 1)
2021-02-10 11:59:19: namespace: npe01
2021-02-10 11:59:19: version: 3.17 (Beta 1)
2021-02-10 11:59:19: name: Install Households 3.14 (Beta 1)
2021-02-10 11:59:19: namespace: npo02
2021-02-10 11:59:19: version: 3.14 (Beta 1)
2021-02-10 11:59:19: - name: Install Recurring Donations 3.21 (Beta 1)
2021-02-10 11:59:19: namespace: npe03
2021-02-10 11:59:19: version: 3.21 (Beta 1)
2021-02-10 11:59:19: - name: Install Relationships 3.11
2021-02-10 11:59:19: namespace: npe4
2021-02-10 11:59:19: version: 3.11
2021-02-10 11:59:19: - name: Install Affiliations 3.9
2021-02-10 11:59:19: namespace: npe5
2021-02-10 11:59:19: version: 3.9
2021-02-10 11:59:19: name: Install Nonprofit Success Pack 3.192 (Beta 17)
2021-02-10 11:59:19: namespace: npsp
2021-02-10 11:59:19: version: 3.192 (Beta 17)
2021-02-10 11:59:19: - name: Deploy unpackaged/post/first
2021-02-10 11:59:19: namespace_inject: npsp
2021-02-10 11:59:19: ref: ef25acd4922895ca89f894c8d3c067302a758a80
2021-02-10 11:59:19: repo_name: NPSP
2021-02-10 11:59:19: repo_owner: SalesforceFoundation
2021-02-10 11:59:19: subfolder: unpackaged/post/first
2021-02-10 11:59:19: Retrieving list of packages from target org
2021-02-10 11:59:19: Pending
2021-02-10 11:59:20: [Pending]: next check in 1 seconds
2021-02-10 11:59:21: [Pending]: next check in 1 seconds
2021-02-10 11:59:23: [Pending]: next check in 2 seconds
2021-02-10 11:59:25: [Pending]: next check in 2 seconds
2021-02-10 11:59:27: [Pending]: next check in 2 seconds
2021-02-10 11:59:30: [Pending]: next check in 3 seconds
2021-02-10 11:59:33: [Done]
2021-02-10 11:59:37: npe01: Install version 3.17 (Beta 1)
2021-02-10 11:59:37: npo02: Install version 3.14 (Beta 1)
2021-02-10 11:59:37: npe03: Install version 3.21 (Beta 1)
2021-02-10 11:59:37: npe4: Install version 3.11
2021-02-10 11:59:37: npe5: Install version 3.9
2021-02-10 11:59:37: npsp: Install version 3.192 (Beta 17)
2021-02-10 11:59:37: Deploying unmanaged metadata from /unpackaged/pre/account_record_types of SalesforceFoundation/NPSP
2021-02-10 11:59:39: Cleaning meta.xml files of packageVersion elements for deploy
2021-02-10 11:59:39: Pending
2021-02-10 11:59:40: [InProgress]: Processing Type: CustomObject
2021-02-10 11:59:42: [InProgress]: Processing Type: CustomObjectTranslation
2021-02-10 11:59:43: [Done]
2021-02-10 11:59:44: [Success]: Succeeded
2021-02-10 11:59:44: Deploying unmanaged metadata from /unpackaged/pre/opportunity_record_types of SalesforceFoundation/NPSP
2021-02-10 11:59:46: Cleaning meta.xml files of packageVersion elements for deploy
2021-02-10 11:59:46: Pending
2021-02-10 11:59:47: [InProgress]: Processing Type: CustomObject
2021-02-10 11:59:49: [Done]
2021-02-10 11:59:50: [Success]: Succeeded
2021-02-10 11:59:50: Installing npe01 version 3.17 (Beta 1)
2021-02-10 11:59:50: Pending
2021-02-10 11:59:51: [Pending]: next check in 1 seconds
2021-02-10 11:59:52: [Pending]: next check in 1 seconds
2021-02-10 11:59:54: [Done]
2021-02-10 11:59:56: [Failed]: Update of InstalledPackage npe01: Error: Mismatching versions
2021-02-10 11:59:56: Exception in task dependencies.update_dependencies
Could not process MDAPI response: Update of InstalledPackage npe01: Error: Mismatching versions
Run this command for more information about debugging errors: cci error --help
michaelkolodner@Michaels-MBP OmbudsmanCloudCare % cci error info
Traceback (most recent call last):
File "/usr/local/Cellar/cumulusci/3.28.0/libexec/lib/python3.8/site-packages/cumulusci/cli/cci.py", line 233, in main
cli(args[1:], standalone_mode=False)
File "/usr/local/Cellar/cumulusci/3.28.0/libexec/lib/python3.8/site-packages/click/core.py", line 829, in __call__
return self.main(*args, **kwargs)
File "/usr/local/Cellar/cumulusci/3.28.0/libexec/lib/python3.8/site-packages/click/core.py", line 782, in main
rv = self.invoke(ctx)
File "/usr/local/Cellar/cumulusci/3.28.0/libexec/lib/python3.8/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/local/Cellar/cumulusci/3.28.0/libexec/lib/python3.8/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/local/Cellar/cumulusci/3.28.0/libexec/lib/python3.8/site-packages/click/core.py", line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/local/Cellar/cumulusci/3.28.0/libexec/lib/python3.8/site-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
File "/usr/local/Cellar/cumulusci/3.28.0/libexec/lib/python3.8/site-packages/cumulusci/cli/cci.py", line 172, in new_func
func(RUNTIME, *args, **kw)
File "/usr/local/Cellar/cumulusci/3.28.0/libexec/lib/python3.8/site-packages/cumulusci/cli/cci.py", line 1772, in flow_run
coordinator.run(org_config)
File "/usr/local/Cellar/cumulusci/3.28.0/libexec/lib/python3.8/site-packages/cumulusci/core/flowrunner.py", line 416, in run
self._run_step(step)
File "/usr/local/Cellar/cumulusci/3.28.0/libexec/lib/python3.8/site-packages/cumulusci/core/flowrunner.py", line 455, in _run_step
raise result.exception # PY3: raise an exception type we control *from* this exception instead?
File "/usr/local/Cellar/cumulusci/3.28.0/libexec/lib/python3.8/site-packages/cumulusci/core/flowrunner.py", line 250, in run_step
task()
File "/usr/local/Cellar/cumulusci/3.28.0/libexec/lib/python3.8/site-packages/cumulusci/core/tasks.py", line 142, in __call__
self.result = self._run_task()
File "/usr/local/Cellar/cumulusci/3.28.0/libexec/lib/python3.8/site-packages/cumulusci/tasks/salesforce/update_dependencies.py", line 140, in _run_task
self._install_dependencies()
File "/usr/local/Cellar/cumulusci/3.28.0/libexec/lib/python3.8/site-packages/cumulusci/tasks/salesforce/update_dependencies.py", line 251, in _install_dependencies
self._install_dependency(dependency)
File "/usr/local/Cellar/cumulusci/3.28.0/libexec/lib/python3.8/site-packages/cumulusci/tasks/salesforce/update_dependencies.py", line 317, in _install_dependency
return api()
File "/usr/local/Cellar/cumulusci/3.28.0/libexec/lib/python3.8/site-packages/cumulusci/salesforce_api/metadata.py", line 70, in __call__
raise MetadataParseError(
cumulusci.salesforce_api.exceptions.MetadataParseError: Could not process MDAPI response: Update of InstalledPackage npe01: Error: Mismatching versions
michaelkolodner@Michaels-MBP OmbudsmanCloudCare %